WO2021057844A1 - 一种创建pm任务的方法及装置 - Google Patents
一种创建pm任务的方法及装置 Download PDFInfo
- Publication number
- WO2021057844A1 WO2021057844A1 PCT/CN2020/117409 CN2020117409W WO2021057844A1 WO 2021057844 A1 WO2021057844 A1 WO 2021057844A1 CN 2020117409 W CN2020117409 W CN 2020117409W WO 2021057844 A1 WO2021057844 A1 WO 2021057844A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- task
- information
- hybrid
- ems
- manager
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/14—Arrangements for monitoring or testing data switching networks using software, i.e. software packages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
Definitions
- the embodiments of the present application relate to the field of communication technologies, and in particular, to a method and device for creating performance management (PM) tasks.
- PM performance management
- VNF virtual network functions
- NS network services
- NS network services
- NS network services
- NS network services
- NS network services
- NS hybrid NS
- PNF physical network function
- PM management is performed on the hybrid NS, PM management of the VNF and PNF contained in the NS is required. PM management needs to create a PM management task (PM Job), which is used to collect corresponding indicators for specific network elements (NE, VNF, PNF).
- the 3rd generation partnership project (3GPP) provides a solution for creating PM management tasks for network elements (NE).
- the solution is marked by the solid arrow in the PM management scenario shown in Figure 1.
- a network manager (NM) issues a request for creating a PM management task for the NE to an element management system (EMS), and the EMS creates a PM management task for the NE according to the content of the request of the NM.
- EMS element management system
- the European Telecommunications Standards Institute provides a solution for creating PM management tasks for hybrid NS.
- the solution is shown by the process marked by the dotted arrow in Figure 1.
- BSS business support system
- NM sends a request to create a PM management task for the NS instance to the network functions virtualization orchestration (NFVO), and NFVO will split the PM management requirements of the NS instance Divided into PM management requirements for NF (VNF and PNF) in the NS instance, a request for creating PM management tasks for VNF and PNF is issued to a network function manager (xNFM).
- xNFM directly establishes PM management tasks for VNF
- xNFM issues a request for creating PM management tasks for PNF to EMS
- EMS establishes PM management tasks for PNF.
- the above two solutions for creating PM management tasks are for different PM management purposes. Both solutions collect PNF performance information through EMS, and create PM management tasks based on the performance management requirements of NE and NS instances. When the two solutions collect the same performance indicators for the same PNF, two management tasks will be created separately through EMS. The objects of these two PM management tasks are both PNF and the collected performance data are the same. The two systems are in the EMS Repeated PM management tasks were created, which caused EMS to deal with redundant PM management tasks when performing performance management, and the management efficiency was not high.
- the embodiments of the present application provide a method and device for creating a PM task, so as to realize efficient PM task management.
- a method for creating a PM task may include: a PM task manager obtains first information and an ID of a hybrid NS, the first information includes identification information of the PNF in the hybrid NS, one or more The identification information of the performance indicators, the information of the collection period, and the information of the reporting period.
- the first information is used to instruct to create one or more performance indicators of the PNF in the first information collected according to the collection period in the first information, and according to the first information
- the report period information in the information reports the collected performance index PM task; the PM task manager sends the first information to the EMS; the PM task manager receives the ID of the first PM task from the EMS; the PM task manager sends the first PM to the EMS
- the PM task manager queries the EMS whether there is a duplicate first PM task, and subscribes to the EMS for the first PM task when the first PM task exists.
- PM task avoid EMS to establish redundant and repetitive PM management tasks when performing performance management, and improve management efficiency.
- the first information and the ID of the hybrid NS can be carried in the first creation request.
- the first creation request is used to request the establishment of the PM task indicated by the information included in the first creation request.
- the PM task indicated by the information included in the first creation request is in accordance with
- the collection period included in the first creation request is collected, one or more performance indicators of the PNF included in the first creation request are collected, and the PM task of the collected performance indicators is reported according to the reporting period information included in the first creation request.
- the function overlap referred to in this article means that the management objects of the two PM tasks are the same, the performance indicators collected are the same, and the PM collection frequency and reporting frequency are the same.
- the life cycles of the overlapping PM tasks may be the same or different, which is not specifically limited in this application.
- the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier can be carried in the subscription request, and the request is marked as a subscription request by the subscription identifier.
- the method for creating a PM task may further include: the PM task manager does not receive the ID of the first PM task, and the PM task manager may send the first PM task to the EMS
- One information and the ID of the hybrid NS are used for the EMS to create the second PM task.
- the PM task manager queries the EMS that there is no duplicate first PM task, the PM task indicated by the information included in the first creation request is created to avoid the EMS from establishing redundancy during performance management Repeated PM management tasks improve management efficiency.
- the first information and the ID of the hybrid NS can be carried in the second creation request.
- the method for creating a PM task may further include: the PM task manager combines the ID of the mixed NS with the first PM The ID of the task corresponds to the record, and the status of the first PM task is marked as subscription. In order to query whether the status of different PM tasks is subscribed or newly created.
- the method for creating a PM task may further include: the PM task manager receives a PM task creation response from the EMS, and the PM The task creation response includes the identification of the second PM task; the PM task manager records the ID of the hybrid NS corresponding to the ID of the second PM task, and marks the status of the second PM task as new. In order to query whether the status of different PM tasks is subscribed or newly created.
- the PM task manager obtains the first information and the ID of the hybrid NS, which can be specifically implemented as follows: the PM task manager receives from the NM The first information and the ID of the hybrid NS; or, the PM task manager receives the first information and the ID of the hybrid NS from NFVO; or, the PM task manager receives the first information and the ID of the hybrid NS from xNFM.
- the PM task manager can be deployed as a functional module in the NM, and the PM task manager receives the first information and The ID of the mixed NS.
- the NM splits the PM task creation request for the hybrid NS into the PM task creation request for the VNF in the hybrid NS and the PM task creation request for the PNF in the hybrid NS.
- the VNF PM task creation request is sent to xNFM through NFVO; the PM task creation request for the PNF in the hybrid NS (including the first information and the ID of the hybrid NS) is sent to the internal PM task manager.
- the PM task manager can be deployed as a functional module in xNFM, and the PM task manager receives the first information and The ID of the mixed NS.
- the NFVO receives the PM task creation request for the hybrid NS from the NM, and the NFVO splits it into the PM task for the VNF in the hybrid NS and the PM task creation request for the PNF in the hybrid NS (including the first A message and the ID of the hybrid NS are sent to xNFM, and the PM task manager deployed in the xNFM receives the first message and the ID of the hybrid NS from the NFVO.
- the PM task manager can be deployed as a separate module between the EMS and xNFM, and the PM task manager can receive from xNFM The first information and the ID of the hybrid NS.
- the NFVO receives the PM task creation request for the hybrid NS from the NM, and the NFVO splits it into the PM task for the VNF in the hybrid NS and the PM task creation request for the PNF in the hybrid NS (including the first A message and the ID of the hybrid NS) and send it to xNFM;
- xNFM is responsible for creating PM tasks for the VNF in the hybrid NS, and sending the PM task creation request for the PNF in the hybrid NS to the PM task manager (including the first Information and the ID of the hybrid NS), the PM task manager deployed between the EMS and xNFM receives the first information and the ID of the hybrid NS from the xNFM.
- the method for creating a PM task may further include: the PM task manager receives the ID of the third PM task, and The ID of the NS and the deletion identification, the deletion identification is used to indicate the deletion of the third PM task for the hybrid NS; if there is no other network element other than the hybrid NS that uses the third PM task, the PM task manager deletes the third PM task through EMS PM task, and delete the recorded correspondence between the third PM task and the ID of the hybrid NS.
- the PM task manager unsubscribes the third PM task, and deletes the recorded ID of the third PM task and the hybrid NS Correspondence. If the third PM task is newly created and other network elements other than the hybrid NS use the third PM task, delete the recorded correspondence between the third PM task and the ID of the hybrid NS.
- the ID of the third PM task, the ID of the hybrid NS, and the deletion identifier can be carried in the deletion request, and the request is marked as a deletion request by the deletion identifier.
- the method may include: the EMS receives first information from the PM task manager, the first information includes identification information of the PNF, identification information of one or more performance indicators, and collection Periodic information, reporting period information; EMS determines that there is a first PM task, and the first PM task collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and according to the first information The reporting period information in the information reports the collected performance indicators of the PM task; EMS sends the identification ID of the first PM task to the PM task manager; EMS receives the ID of the first PM task, the ID of the hybrid NS and the subscription from the PM task manager Identifier, the subscription identifier is used to subscribe to the first PM task for the hybrid NS.
- the PM task manager queries the EMS whether there is a duplicate first PM task, and subscribes to the EMS for the first PM task when the first PM task exists.
- PM task avoid EMS to establish redundant and repetitive PM management tasks when performing performance management, and improve management efficiency.
- the method for creating a PM task may further include: after the EMS executes the first PM task, according to the reporting period information, report one or more of the PNF collected for the hybrid NS to the PM task manager Performance. Or, after executing the first PM task, the EMS reports one or more performance indicators of the PNF collected for the hybrid NS to the NM according to the reporting period information.
- the method for creating a PM task may further include: if the first PM task does not exist, the EMS receives the first information and the ID of the hybrid NS from the PM task manager The EMS creates a second PM task, the second PM task is the PM task indicated by the first information; the EMS sends a PM task creation response to the PM manager, and the PM task creation response includes the identifier of the second PM task.
- the method for creating a PM task may further include: the EMS receives the ID of the third PM task from the PM task manager , The ID of the hybrid NS and the unsubscription identifier; after the EMS executes the third PM task, it stops reporting the performance indicators of the third PM task collected for the hybrid NS.
- the ID of the third PM task, the ID of the hybrid NS, and the unsubscribe identifier can be carried in the unsubscribe request, and the request is marked as an unsubscribe request by the unsubscribe identifier.
- the method for creating a PM task may further include: the EMS receives the ID of the third PM task from the PM task manager , Hybrid NS ID and deletion identification; EMS deletes the third PM task.
- the ID of the third PM task, the ID of the hybrid NS, and the deletion identifier can be carried in the deletion request, and the request is marked as a deletion request by the deletion identifier.
- a device for creating a PM task can be a PM task manager.
- the PM task manager can be deployed inside an NM or xNFM, or between xNFM and EMS.
- the device can be a chip system.
- the device can realize the functions performed by the PM task manager in the above-mentioned aspects or various possible designs, and the functions can be realized by hardware, or by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above-mentioned functions.
- the device for creating a PM task may include: an acquiring unit, a sending unit, and a receiving unit.
- the acquiring unit is configured to acquire first information and the identification ID of the NS.
- the first information includes identification information of the physical network function PNF in the NS, identification information of one or more performance indicators, information about the collection period, and information about the reporting period.
- Information; the first information is used to instruct to create a PM that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information task.
- the sending unit is used to send the first information to the EMS.
- the receiving unit is configured to receive the ID of the first PM task from the EMS.
- the first PM task collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and according to the first information
- the report period information is reported to the PM task of the collected performance indicators.
- the sending unit is further configured to send the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier to the EMS, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS.
- the device for creating a PM task provided by the third aspect is used to execute the method for creating a PM task provided by the first aspect.
- the device for creating a PM task provided by the third aspect is used to execute the method for creating a PM task provided by the first aspect.
- the device may be an EMS, or may be a device or chip system deployed in the EMS.
- the device can realize the functions performed by the EMS in the above-mentioned aspects or various possible designs, and the functions can be realized by hardware, or by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above-mentioned functions.
- the device for creating a PM task may include: a receiving unit, a judging unit, and a sending unit.
- the receiving unit is configured to receive the first information from the PM task manager, the first information includes identification information of the PNF, identification information of one or more performance indicators, information about the collection period, and information about the reporting period.
- the determining unit is used to determine that there is a first PM task, and the first PM task collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and according to the reporting period in the first information Information is reported to the PM task of the collected performance indicators.
- the sending unit is used to send the identification ID of the first PM task to the PM task manager.
- the receiving unit is further configured to receive the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier from the PM task manager, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS.
- the device for creating a PM task provided by the fourth aspect is used to execute the method for creating a PM task provided by the second aspect.
- the device for creating a PM task provided by the fourth aspect is used to execute the method for creating a PM task provided by the second aspect.
- the present application provides a PM task manager.
- the PM task manager may include: a processor, a memory; the processor, and the memory are coupled, and the memory may be used to store computer program codes.
- the computer program codes include computer instructions. When the instruction is executed by the PM task manager, the PM task manager is caused to execute the method for creating a PM task as described in the first aspect or any possible implementation manner.
- this application provides an EMS.
- the EMS may include: a processor, a memory; a processor, and a memory coupling.
- the memory may be used to store computer program codes.
- the computer program codes include computer instructions. When the computer instructions are executed by the EMS, The EMS is made to execute the method for creating a PM task as described in the second aspect or any one of the possible implementation manners.
- the present application provides a computer-readable storage medium.
- the computer-readable storage medium may include: computer software instructions; when the computer software instructions run in the PM task manager, the PM task manager executes The method for creating a PM task described in one aspect or any one of the possible implementation manners of the first aspect.
- the present application provides a computer-readable storage medium.
- the computer-readable storage medium may include: computer software instructions; when the computer software instructions run in the EMS, the EMS is made to execute the second aspect or the second aspect.
- the method for creating a PM task described in any one of the possible implementation manners.
- this application provides a computer program product, which when the computer program product runs on a computer, causes the computer to execute any one of the first aspect or the second aspect or any one of the possible implementation manners of the claims.
- the present application provides a chip system that is applied to a PM task manager or EMS; the chip system includes an interface circuit and a processor; the interface circuit and the processor are interconnected through a line; the interface circuit is used to slave the PM task.
- the manager or the memory of the EMS receives the signal and sends the signal to the processor.
- the signal includes the computer instruction stored in the memory; when the processor executes the computer instruction, the chip system executes the first aspect or the second aspect or any one of them.
- the method for creating a PM task described in any one of the implementation manners.
- this application provides a PM management system, including a PM task manager and an EMS.
- the PM task manager executes the creation of a PM task as described in the first aspect or any one of the possible implementation manners of the first aspect.
- the EMS executes the method for creating a PM task as described in the second aspect or any one of the possible implementation manners of the second aspect.
- Figure 1 is a schematic diagram of a PM management scenario
- FIG. 2 is a schematic flow diagram of the PM management process in ETSI
- FIG. 3 is a schematic structural diagram of a PM management system framework provided by an embodiment of this application.
- FIG. 4 is a schematic structural diagram of a communication device provided by an embodiment of this application.
- FIG. 5 is a schematic flowchart of a method for creating a PM task provided by an embodiment of the application
- FIG. 6 is a schematic flowchart of another method for creating a PM task provided by an embodiment of the application.
- FIG. 7 is a schematic structural diagram of an apparatus for creating a PM task provided by an embodiment of the application.
- FIG. 8 is a schematic structural diagram of another device for creating a PM task provided by an embodiment of the application.
- FIG. 9 is a schematic structural diagram of another device for creating a PM task provided by an embodiment of the application.
- FIG. 10 is a schematic structural diagram of another device for creating a PM task provided by an embodiment of the application.
- words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not limit the difference.
- the “first” and second description of the technical features have no order or size order.
- words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner to facilitate understanding.
- A/B can mean A or B; the "and/or” in this application is only It is a kind of association relationship that describes the associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B It can be singular or plural.
- plural means two or more than two.
- the following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
- at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
- At least one may also be described as one or more, and the multiple may be two, three, four or more, which is not limited in the present application.
- A sends certain content to B.
- the content can be forwarded level by level through the network element between A and B, so that the content Arrive at B, which is uniformly described in this article as "A sends the content to B".
- a PM task with overlapping functions means that the management objects of the two PM tasks are the same, the collected performance indicators overlap, and the PM collection frequency and reporting frequency are the same.
- the overlap of the collected performance indicators includes the same collected performance indicators, and the collected performance indicators can be converted to each other.
- the life cycles of the overlapping PM tasks can be the same or different.
- PM management usually first creates a PM management task (PM Job), and collects the performance indicators of the VNF and PNF in the NS for network operation and maintenance by performing the PM management task.
- PM Job PM management task
- the NM triggers the start of the PM management process.
- the PM management requirement can be performed according to the configuration of the system administrator, which is not specifically limited in the embodiment of the present application.
- the process of PM management in ETSI can refer to the agreement GS-IFA010. As shown in Figure 2, the process of PM management in ETSI can include:
- the NM sends a PM task creation request to the NFVO.
- the PM task creation request may include: NS identification, information of one or more performance indicators, information of collection period, information of reporting period, and life cycle information.
- the parameters included in the PM task creation request may be as shown in Table 1.
- the NFVO creates an ID for the PM task of the NS.
- the NFVO sends a PM task establishment response message to the NM.
- the PM task establishment response message includes the ID of the PM task for NS created by NFVO.
- S204 and NFVO split the PM task for NS into PM tasks for VNF and PNF.
- the NFVO records the VNF and PNF included in different NSs, and S204 splits the PM task for the NS into the PM task for the VNF and PNF according to the VNF and PNF included in the recorded NS.
- NFVO sends a PM task creation request to xNFM.
- the data of the PM task creation request in S205 is the same as the total amount of VNF and PNF included in the NS, that is, the NFVO in S205 sends a PM task creation request for each VNF and PNF in the NS.
- the PM task creation request includes the identification of the VNF or PNF, the information of one or more performance indicators, the information of the collection period, the information of the reporting period, and the life cycle information.
- the xNFM creates a PM task for the VNF and executes the PM task for the VNF.
- the PM task for the VNF is executed, that is, in the life cycle of the PM task for the VNF, the performance information of one or more performance indicators is collected according to the collection cycle, and the collected performance information is reported to the NM through the NFVO according to the reporting cycle.
- the xNFM sends a PM task creation request for the PNF to the EMS.
- the PM task creation request includes the identification of the PNF, the information of one or more performance indicators, the information of the collection period, the information of the reporting period, and the NS identification.
- the EMS creates a PM task for the PNF and executes the PM task for the VNF.
- the execution of the PM task for PNF that is, in the life cycle of the PM task for PNF, the performance information of one or more performance indicators is collected according to the collection cycle, and the collected performance information is reported to the NM through xNFM and NFVO according to the reporting cycle .
- 3GPP provides a solution for creating PM management tasks for NEs.
- NM issues a request to EMS to create PM management tasks for NEs.
- EMS creates and executes PM management tasks for NEs based on the content of the NM’s request.
- the solutions provided by ETSI and ETSI collect PNF performance information through EMS. It may happen that the two systems create repeated PM management tasks in EMS, causing EMS to deal with redundant PM management tasks when performing performance management, and management efficiency. not tall.
- the basic principle of the solution provided by this application is: When the PM task manager receives a new request to create a PM task, it first confirms whether the requested PM task overlaps with the existing PM task function, and if it overlaps, it directly subscribes. No new creation is required, which avoids the EMS from establishing redundant and repetitive PM management tasks when performing performance management, and improves management efficiency.
- the solution provided in this application can be applied to the framework of the PM management system shown in FIG. 3, and the framework can be applied to any communication system.
- the communication system can be a 3rd generation partnership project (3rd generation partnership project, 3GPP) communication system, for example, a long term evolution (LTE) system, or a fifth generation mobile communication system (the 5th, 5G) Or a new radio (NR) system, or a non-3GPP communication system, is not restricted.
- 3rd generation partnership project 3rd generation partnership project, 3GPP
- LTE long term evolution
- NR new radio
- the PM management system includes NM 301, NFVO 302, xNFM 303, PM task manager 304, and EMS 305.
- the PM management system is used to manage NS 306.
- NS 306 includes PNF 3061 and VNF 3062.
- the PM task manager 304 is the core network element of this application, responsible for querying and managing existing PM Jobs.
- the PM task manager 304 can be deployed as a functional network element inside the NM 301 (position 1 in Figure 3), or deployed as a functional network element inside the xNFM 303 (position 2 in Figure 3), or as a separate
- the module is deployed between xNFM 303 and EMS 305 (position 3 in Figure 3).
- NM 301 is an integrated and information resource sharing support system for telecom operators. It is mainly composed of network management, system management, billing, business, accounting, and customer service. The systems are organically integrated through a unified information bus. At the same time, a PM management request for the NS 206 instance is sent to NFVO 302.
- the NM 301 may be an operation support system (OSS)/business support system (BSS).
- OSS operation support system
- BSS business support system
- NFVO 302 is responsible for creating the PM Job for the entire NS 306 instance, decomposes the PM management requirements for the NS 306 instance into the management requirements for PNF 3061 and VNF 3062 in the NS 306 instance, and delivers it to xNFM 303.
- xNFM 303 is responsible for creating a PM Job for VNF 3062 according to the requirements of NFVO 302, and creating a PM Job for PNF 3061 through EMS 305 according to the requirements issued by NFVO 302.
- EMS 305 is a system for managing one or more telecommunications network elements of a specific type. It is independently developed by each company and is responsible for managing the PNF and VNF of each company, creating PM Jobs according to requirements, and collecting information corresponding to PNF.
- 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.
- the architecture of the PM management system shown in FIG. 3 is only an exemplary architecture diagram, and the number of network elements and the names of the network elements included in the PM management system are not limited.
- the PM management system shown in FIG. 3 may also include other network elements.
- the network element and the name of each network element in the above-mentioned FIG. 3 architecture are just an example, and the name of the network element in a specific implementation may be other, which is not specifically limited in the embodiment of the present application.
- FIG. 4 is a schematic diagram of the composition of a communication device 40 provided by an embodiment of the application.
- the communication device 40 may include at least one processor 41, a memory 42, a communication interface 43, and a communication bus 44.
- processor 41 a processor 41
- memory 42 a memory
- communication interface 43 a communication interface
- communication bus 44 a communication bus 44
- the processor 41 may be one processor or a collective name for multiple processing elements.
- the processor 41 is a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application
- CPU central processing unit
- ASIC application specific integrated circuit
- microprocessors digital signal processors, DSP
- FPGA field programmable gate arrays
- the processor 41 can execute various functions of the function alias control server by running or executing a software program stored in the memory 42 and calling data stored in the memory 42.
- the processor 41 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 4.
- the communication device 40 may include multiple processors, such as the processor 41 and the processor 45 shown in FIG. 4.
- processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
- the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
- the memory 42 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
- the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
- the memory 42 may exist independently, and is connected to the processor 41 through a communication bus 44.
- the memory 42 may also be integrated with the processor 41. Among them, the memory 42 is used to store a software program for executing the solution of the present application, and is controlled and executed by the processor 41.
- the communication interface 43 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
- the communication interface 43 may include a receiving unit and a sending unit.
- the communication bus 44 may be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus.
- ISA industry standard architecture
- PCI peripheral component
- EISA extended industry standard architecture
- the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used to represent in FIG. 4, but it does not mean that there is only one bus or one type of bus.
- the components shown in FIG. 4 do not constitute a limitation on the communication device.
- the communication device may include more or less components than those shown in the figure, or a combination of certain components. Some components, or different component arrangements.
- the communication device 40 can be used as a PM task manager, and the processor 41 executes the following functions by running or executing software programs and/or modules stored in the memory 42 and calling data stored in the memory 42 :
- the first information includes the identification information of the PNF in the hybrid NS, the identification information of one or more performance indicators, the information of the collection period, and the information of the reporting period; send to the EMS through the communication interface 43 First information; the identification ID of the first PM task is received from the EMS through the communication interface 43, and the ID of the first PM task, the ID of the hybrid NS and the subscription identification are sent to the EMS through the communication interface 43, and the subscription identification is used for the hybrid NS Subscribe to the first PM task.
- the first PM task is a PM task that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information.
- the communication device 40 can be used as an EMS, and the processor 41 executes the following functions by running or executing software programs and/or modules stored in the memory 42 and calling data stored in the memory 42:
- the first information includes identification information of the PNF, identification information of one or more performance indicators, information about the collection period, and information about the reporting period; it is determined that the first PM task exists,
- the first PM task is a PM task that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information; through communication
- the interface 43 sends the identification ID of the first PM task to the PM task manager.
- an embodiment of the present application provides a method for creating a PM task, which is applied in the PM management process.
- the NM When the NM has PM management requirements, it triggers the start of the PM management process.
- the solution provided in this application is to split the PM task for the NS into the PM task for the VNF and PNF in the NS, and then the PM task for the PNF
- the method for creating a PM task may include:
- the PM task manager obtains the first information and the ID of the hybrid NS.
- the first information and the ID of the hybrid NS may be carried in the first creation request for the PNF in the hybrid NS.
- the first information is used to request the creation of the PM task indicated by the first information.
- the PM task indicated by the first information is the PM that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information task.
- the PM task manager in S501 obtains the first information and the ID of the hybrid NS in different ways, including but not limited to the following three possible implementations:
- the PM task manager receives the first information and the ID of the hybrid NS from the NM.
- the PM task manager can be deployed in the NM as a functional module, and the PM task manager receives the first information and the ID of the hybrid NS from the inside of the NM.
- the NM splits the PM task creation request for the hybrid NS into a PM task for the VNF in the hybrid NS and a PM task creation request for the PNF in the hybrid NS (including the first information and the hybrid NS ID), send the PM task creation request for the VNF in the hybrid NS to xNFM through NFVO; send the PM task creation request for the PNF in the hybrid NS (including the first information and the ID of the hybrid NS) to Internal PM task manager.
- the NM splits the PM task creation request for the hybrid NS into the PM task creation request for the VNF in the hybrid NS and the PM task creation request for the PNF in the hybrid NS can be the same as the NFVO in S204. Let me repeat it again.
- the PM task manager receives the first information and the ID of the hybrid NS from the NFVO.
- the PM task manager can be deployed as a functional module in xNFM.
- NFVO receives a PM task creation request for the hybrid NS from the NM (same as the aforementioned S201), and NFVO splits it into a VNF for the hybrid NS.
- the PM task and the PM task creation request for the PNF in the hybrid NS (the same as the aforementioned S204, including the first information and the ID of the hybrid NS), and sent to xNFM (the same as the aforementioned S205), and deployed in the PM task in xNFM
- the manager receives the ID including the first information and the hybrid NS from the NFVO.
- the PM task manager receives the ID including the first information and the hybrid NS from the xNFM.
- the PM task manager can be deployed as a separate module between the EMS and xNFM.
- NFVO receives the PM task creation request for the hybrid NS from the NM (the same as the aforementioned S201), and the NFVO splits it into The PM task of the VNF in the hybrid NS and the creation request for the PM task of the PNF in the hybrid NS (the same as the aforementioned S204, including the first information and the ID of the hybrid NS), and sent to xNFM (the same as the aforementioned S205);
- xNFM is responsible Create a PM task for the VNF in the hybrid NS, and send a PM task creation request for the PNF in the hybrid NS (including the first information and the ID of the hybrid NS) to the PM task manager, which is deployed between the EMS and xNFM
- the PM task manager receives the ID including the first information and the hybrid NS from the xNFM.
- the PM task manager sends the first information to the EMS.
- the first information can be carried in the PM task matching request and sent.
- the first information sent in S502 is used to request the EMS to determine whether there is an established PM task that overlaps with the PM task function indicated by the first information. .
- a matching identifier can be carried, which is used to indicate that the first information sent is used to request the EMS to determine whether there is an established PM task that corresponds to the PM task indicated by the first information.
- PM tasks with overlapping functions are used to indicate that the first information sent.
- the first information sent in S502 may be exactly the same as the first information obtained in S501, or it may be the first information after the conversion of the performance indicators included in the first information obtained in S501.
- the implementation of this application The example does not specifically limit this.
- 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 will not be repeated here.
- the EMS determines whether there is a first PM task.
- the EMS records the information of each PM task that has been established.
- the EMS judges whether the first PM task exists according to the recorded information.
- the first PM task is a PM task that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information. That is, the function of the first PM task overlaps with the PM task indicated by the first information.
- 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.
- the EMS determines whether there is a first PM task.
- the EMS when the EMS determines that the first PM task exists, and the life cycle of the first PM task is earlier than the boundary time of the life cycle of the PM task indicated by the first information, the EMS also needs to modify the first PM task For the life cycle, the boundary time of the life cycle of the PM task indicated by the first information is taken as the boundary time of the life cycle of the first PM task.
- the EMS sends the ID of the first PM task to the PM task manager.
- the ID of the first PM task may be carried in the PM task matching response.
- the PM task manager receives the 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 the subscription identifier to the EMS.
- the ID of the hybrid NS sent in S507 is the ID of the hybrid NS obtained in S501.
- the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier may be carried in the subscription request, and the request is marked as a subscription request by the subscription identifier.
- the operation of S507 is used to subscribe the first PM task to the EMS, so that after executing the first PM task, the EMS reports the performance information collected by the first PM task according to the reporting period of the first PM task as the PM for the hybrid NS Manage data.
- the EMS receives the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier from the PM task manager.
- the ID of the first PM task, the ID of the hybrid NS and the subscription identifier received by the EMS in S508 are the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier sent by the PM task manager in S507. Go into details again.
- the EMS reports the performance information collected by executing the first PM task according to the reporting period of the first PM task as PM management data for the hybrid NS included in the subscription request.
- the PM task manager queries the EMS whether there is a duplicate first PM task, and subscribes to the EMS for the first PM task when the first PM task exists.
- PM task avoid EMS to establish redundant and repetitive PM management tasks when performing performance management, and improve management efficiency.
- the method for creating a PM task provided in the embodiment of the present application may further include S509.
- the EMS After executing the first PM task, the EMS reports the collected performance index of the first PM task according to the reporting period of the first PM task.
- the EMS reports the collected performance indicators of the first PM task to the PM task manager according to the reporting period of the first PM task, and the reported performance indicators are used as A performance report for the PNF of the hybrid NS included in the first creation request to manage the hybrid NS included in the first creation request.
- the EMS reports the collected performance indicators of the first PM task to the PM task manager according to the reporting period of the first PM task.
- the PM task manager is deployed in xNFM or xNFM
- the NFVO combines the performance report for the PNF and the performance report for the VNF collected by xNFM into a performance report for the hybrid NS and sends an NM.
- the EMS reports the collected performance indicators of the first PM task to the network manager NM according to the reporting period of the first PM task, and the reported performance indicators As a performance report of the PNF for the hybrid NS included in the first creation request to manage the hybrid NS.
- the EMS reports the collected performance indicators of the first PM task to the NM according to the reporting period of the first PM task, and the reported performance indicators are included in the first creation request.
- the NM For the performance report of the PNF of the hybrid NS, the NM combines the performance report for the PNF and the performance report for the VNF collected by xNFM into a performance report for the hybrid NS.
- the method for creating a PM task provided in the embodiment of the present application may further include S510.
- the PM task manager records the ID of the hybrid NS corresponding to the ID of the first PM task, and marks the status of the first PM task as subscription.
- the first PM task is recorded as the subscription state, which is convenient for subsequent cancellation or deletion.
- the method for creating a PM task may further include S511-S516.
- the PM task manager sends 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 creation identifier may also be carried, and the creation identifier is used to indicate that the EMS is used to create the second PM task.
- the first information sent in S511 may be exactly the same as the first information obtained in S501, or it may be the first information after the conversion of the performance indicators included in the first information obtained in S501.
- the implementation of this application The example does not specifically limit this.
- the EMS receives the first information and the ID of the hybrid NS from the PM task manager.
- the first information received by the EMS in S512 and the ID of the hybrid NS are the first information and the ID of the hybrid NS sent by the PM task manager in S511, which will not be repeated here.
- the process of creating a PM task by the EMS in S513 can refer to the protocol 3GPP32412, which is not described in detail in the embodiment of the present application.
- the EMS sends a PM task creation response to the PM task manager.
- the PM task creation response includes the identification of the second PM task, and the PM task creation response is used to notify the PM task manager that the establishment of the second PM task has been completed.
- the PM task manager receives the 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, which will not be repeated here.
- the PM task manager records the ID of the hybrid NS corresponding to the ID of the second PM task, and marks the status of the second PM task as new.
- the second PM task is recorded as a subscription state through S516, which is convenient for subsequent unsubscription or deletion.
- the PM task manager may record the status information shown in Table 2.
- the status information records the status of different PM tasks for different NSs, which is convenient for subsequent unsubscription or deletion.
- the above process describes the process of subscribing to or creating PM tasks according to PM management requirements in the PM management process.
- PM management process some PM tasks that are being executed need to be deleted according to PM management requirements.
- the deletion process of PM tasks is described below. As shown in Figure 6, the PM task deletion process may include part or all of S517-S523.
- the method also includes:
- the PM task manager receives the ID of the third PM task, the ID of the hybrid NS, and the deletion identifier.
- the way that the PM task manager receives the ID of the third PM task, the ID of the hybrid NS, and the deletion identifier is similar to the way the PM task manager receives the first information and the ID of the hybrid NS in S501. Go into details again.
- the deletion operation is specifically performed according to the recorded state of the third PM task for the hybrid NS included in the deletion request.
- the PM task manager can query the status information as shown in Table 2, and select a different subsequent implementation to delete the state of the third PM task of the hybrid NS included in the delete request. operating.
- the PM task manager deletes the third PM task through the EMS, and deletes the recorded correspondence between the third PM task and the ID of the hybrid NS.
- the PM task manager sends a deletion request to the EMS.
- the deletion request includes the ID of the third PM task and is used to instruct the EMS to delete the third PM task.
- the EMS deletes the third PM task, and then no longer executes the third PM task.
- the PM task manager cancels the subscription of the third PM task, and deletes the recorded correspondence between the third PM task and the ID of the hybrid NS.
- the PM task manager sends the ID of the third PM task, the ID of the hybrid NS, and the unsubscribe flag to the EMS to instruct the EMS to no longer report the performance of the third PM task of the PNF for the hybrid NS report.
- the EMS receives the ID of the third PM task, the ID of the hybrid NS, and the unsubscription identifier from the PM task manager.
- the PM task manager unsubscribes the third PM task from the EMS. After the EMS executes the third PM task, it will no longer report the performance indicators for the third PM task of the hybrid NS included in the unsubscribe request, but The performance indicators of the third PM task for other network elements that use the third PM task are also reported.
- the PM task manager deletes the recorded correspondence between the third PM task and the ID of the hybrid NS.
- the PM task manager only needs to delete the correspondence between the internally recorded third PM task and the ID of the hybrid NS included in the deletion request in S517, and does not need to exchange any information with the EMS.
- the PM task manager After S518 and S519, or S520-S522, or S523, the PM task manager also needs to feed back the response message of the deletion request in S517 to notify that the third PM task has been deleted.
- the foregoing mainly introduces the solution provided by the embodiment of the present application from the perspective of the working principle of the PM task manager and the EMS.
- the PM task manager and the EMS include hardware structures and/or software modules corresponding to the respective functions.
- the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
- the embodiment of the present application can divide the PM task manager and the EMS into functional modules according to the above method examples.
- each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
- the above-mentioned integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
- an apparatus 70 for creating a PM task provided by an embodiment of the present application is used to implement the function of the PM task manager in the above method.
- the device 70 for creating a PM task may be a PM task manager deployed in the NM or xNFM, or may also be a PM task manager deployed between the xNFM and the EMS.
- the device 70 for creating a PM task may be a chip system.
- the chip system may be composed of chips, or may include chips and other discrete devices.
- the apparatus 70 for creating a PM task may include: an acquiring unit 7001, a sending unit 7002, and a receiving unit 7003.
- the obtaining unit 7001 is used to execute S501 in FIG. 5 or FIG. 6, the sending unit 7002 is used to execute S502, S507, and S511 in FIG. 5 or FIG. 6, and the receiving unit 7003 is used to execute S506, S515 in FIG. 5 or FIG. , S517.
- S501 in FIG. 5 or FIG. 6 the sending unit 7002 is used to execute S502, S507, and S511 in FIG. 5 or FIG. 6, and the receiving unit 7003 is used to execute S506, S515 in FIG. 5 or FIG. , S517.
- the apparatus 70 for creating a PM task may further include a processing unit 7004 for executing S510, S516, S518, S520, and S523 in FIG. 6.
- an apparatus 80 for creating a PM task provided by an embodiment of the present application is used to implement the function of the PM task manager in the above method.
- the device 80 for creating a PM task can be a PM task manager deployed in NM or xNFM, or can also be a PM task manager deployed between xNFM and EMS.
- the device 80 for creating the PM task may be a chip system.
- the chip system may be composed of chips, or may include chips and other discrete devices.
- the device 80 for creating a PM task includes at least one processing module 801 and a communication module 802.
- the processing module 801 may be used to execute the processes S501, S510, S516, S518, S520, S523 in FIG. 5 or FIG. 6; the processing module 801 may be used to execute the processes in FIG. 5 or FIG. 6 through the communication module 802 S502, S506, S507, S511, S515, S517.
- the communication module 802 S502, S506, S507, S511, S515, S517.
- the device 80 for creating a PM task may also include at least one storage module 803 for storing program instructions and/or data.
- the storage module 803 and the processing module 801 are coupled.
- the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
- the processing module 801 may cooperate with the storage module 802 to operate.
- the processing module 801 may execute program instructions stored in the storage module 802. At least one of the at least one storage module may be included in the processing module.
- the processing module 801 is a processor
- the communication module 802 is a transceiver
- the storage module 803 is a memory
- the device 80 for creating a PM task involved in FIG. 8 of the embodiment of the present application may be the communication device 40 shown in FIG. 4.
- the device 70 for creating a PM task or the device 80 for creating a PM task provided by the embodiments of the present application can be used to implement the function of the PM task manager in the method implemented by the various embodiments of the present application.
- the device 70 for creating a PM task or the device 80 for creating a PM task provided by the embodiments of the present application can be used to implement the function of the PM task manager in the method implemented by the various embodiments of the present application.
- the device 70 for creating a PM task or the device 80 for creating a PM task provided by the embodiments of the present application can be used to implement the function of the PM task manager in the method implemented by the various embodiments of the present application.
- the parts related to the embodiments of the present application if the specific technical details are not disclosed, please refer to the various embodiments of the present application.
- an apparatus 90 for creating a PM task provided by an embodiment of the present application is used to implement the function of the EMS in the above method.
- the device 90 for creating the PM task may be an EMS, or a device in the EMS, or a device that can be matched and used with the EMS.
- the device 90 for creating the PM task may be a chip system.
- the chip system may be composed of chips, or may include chips and other discrete devices.
- the apparatus 90 for creating a PM task may include: a receiving unit 9001, a determining unit 9002, and a sending unit 9003.
- the receiving unit 9001 is used to execute S503, S508, S512, and S521 in FIG. 5 or FIG. 6, the determining unit 9002 is used to execute S504 in FIG. 5 or FIG. 6, and the sending unit 9003 is used to execute S504 in FIG. 5 or FIG. S505, S514.
- all relevant content of the steps involved in the above method embodiments can be cited in the functional description of the corresponding functional module, which will not be repeated here.
- the apparatus 90 for creating a PM task may further include a processing unit 9004 for executing S509, S513, S519, and S523 in FIG. 6.
- an apparatus 100 for creating a PM task provided in an embodiment of the present application is used to implement the function of the EMS in the above method.
- the device 100 for creating a PM task may be an EMS, a device in the EMS, or a device that can be used in conjunction with the EMS.
- the device 100 for creating a PM task may be a chip system.
- the chip system may be composed of chips, or may include chips and other discrete devices.
- the apparatus 100 for creating a PM task includes at least one processing module 1001 and a communication module 1002.
- the processing module 1001 may be used to execute the processes S504, S509, S513, S519, and S523 in FIG. 5 or FIG. 6; the processing module 1001 may be used to execute the processes S503, S503, S503, and S503 in FIG. 5 or FIG. 6 through the communication module 1002.
- S505, S508, S512, S514, S521. For details, please refer to the detailed description in the method example, which will not be repeated here.
- the apparatus 100 for creating a PM task may further include at least one storage module 1003 for storing program instructions and/or data.
- the storage module 1003 and the processing module 1001 are coupled.
- the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
- the processing module 1001 may operate in cooperation with the storage module 1002.
- the processing module 1001 may execute program instructions stored in the storage module 1002. At least one of the at least one storage module may be included in the processing module.
- the processing module 1001 is a processor
- the communication module 1002 is a transceiver
- the storage module 1003 is a memory
- the device 100 for creating a PM task involved in FIG. 10 of the embodiment of the present application may be the communication device 40 shown in FIG. 4.
- the device 90 for creating a PM task or the device 100 for creating a PM task can be used to implement the functions of the EMS in the methods implemented by the various embodiments of the present application.
- the relevant parts of the application embodiment if the specific technical details are not disclosed, please refer to the various embodiments of the application.
- FIG. 5 Another embodiments of the present application further provide a computer-readable storage medium, which may include computer software instructions, which when the computer software instructions run on the PM task manager, cause the PM task manager to execute the above The steps performed by the PM task manager in the embodiment shown in FIG. 5 or FIG. 6.
- a computer-readable storage medium which may include computer software instructions, which when the computer software instructions run on the PM task manager, cause the PM task manager to execute the above The steps performed by the PM task manager in the embodiment shown in FIG. 5 or FIG. 6.
- FIG. 5 may be a block diagram illustrating an exemplary computing environment in accordance with the present application.
- FIG. 6 may be a block diagram illustrating an exemplary computing environment in accordance with the present application.
- FIG. 5 or FIG. 6 Other embodiments of the present application also provide a computer program product, when the computer program product runs on a computer, the computer is caused to execute the steps performed by the PM task manager or the EMS in the embodiment shown in FIG. 5 or FIG. 6 .
- the chip system includes an interface circuit and a processor; the interface circuit and the processor are interconnected by wires; the interface circuit is used to receive signals from the memory of the terminal and send signals to the processor.
- the signals include computer instructions stored in the memory; when the processor executes When the computer is instructed, the chip system executes the steps executed by the PM task manager or the EMS in the embodiment shown in FIG. 5 or FIG. 6 above.
- the steps of the method or algorithm described in combination with the disclosure of this application can be implemented in a hardware manner, or can be implemented in a manner in which a processor executes software instructions.
- Software instructions can be composed of corresponding software modules.
- the software modules can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (erasable programmable ROM, EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EPROM, EEPROM), registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art.
- An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium.
- the storage medium may also be an integral part of the processor.
- the processor and the storage medium may be located in the ASIC.
- the ASIC may be located in the core network interface device.
- the processor and the storage medium may also exist as discrete components in the core network interface device.
- the memory may be coupled with the processor.
- the memory may exist independently and be connected to the processor through a bus.
- the memory can also be integrated with the processor.
- the memory may be used to store application program codes that execute the technical solutions provided in the embodiments of the present application, and the processor controls the execution.
- the processor is used to execute the application program code stored in the memory, so as to implement the technical solution provided in the embodiment of the present application.
- the disclosed device and method can be implemented in other ways.
- the device embodiments described above are merely illustrative.
- the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be divided. It can be combined or integrated into another device, or some features can be omitted or not implemented.
- the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
- the units described as separate parts may or may not be physically separate.
- the parts displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
- the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
- the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
- the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium.
- the technical solutions of the embodiments of the present application are essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of a software product, and the software product is stored in a storage medium. It includes several instructions to make a device (may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the method described in each embodiment of the present application.
- the aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请实施例公开了一种创建PM任务的方法及装置,涉及通信技术领域,以实现高效的PM任务管理。具体方案包括:PM任务管理器获取第一信息及混合NS的ID;PM任务管理器向EMS发送第一信息;PM任务管理器从EMS接收第一PM任务的ID,PM任务管理器向EMS发送第一PM任务的ID、混合NS的ID及订阅标识。其中,第一PM任务是按照第一信息中的收集周期,搜集第一信息中的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任务。
Description
本申请要求于2019年09月27日提交国家知识产权局、申请号为201910928046.2、发明名称为“一种创建PM任务的方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请实施例涉及通信技术领域,尤其涉及一种创建性能管理(performance management,PM)任务的方法及装置。
随着网络功能虚拟化(network functions nirtualization,NFV)技术的快速发展,虚拟网络功能(virtual network function,VNF)已经大量部署于通信网络中。
目前,通信网络中存在两种不同类型的网络服务(network service,NS)。一种是完全由VNF构成的NS;另一种是由VNF和物理网络功能(physical network function,PNF)构成的NS(混合NS),对应部分物理网元无法虚拟化的场景。对混合NS进行PM管理时,要对该NS中包含的VNF和PNF进行PM管理。PM管理需创建PM管理任务(PM Job),PM管理任务用于针对特定的网元(NE、VNF、PNF)搜集对应指标。
第三代合作伙伴计划(3rd generation partnership project,3GPP)提供了一种针对网元(net element,NE)创建PM管理任务的方案,该方案如图1示意的PM管理场景中的实线箭头标注的流程,网络管理器(network manager,NM)向网元管理***(element management system,EMS)下达针对NE创建PM管理任务的请求,EMS根据NM的请求内容,建立针对该NE的PM管理任务。
欧洲电信标准协会(european telecommunications standards institute,ETSI)提供了一种针对混合NS创建PM管理任务的方案,该方案如图1中虚线箭头标注的流程,运营支撑***(operation support system,OSS)/业务支撑***(business support system,BSS)(NM)向网络功能虚拟化编排器(network functions virtualization orchestration,NFVO)发送创建针对NS实例的PM管理任务的请求,NFVO将针对该NS实例的PM管理需求拆分为针对NS实例中的NF(VNF和PNF)的PM管理需求,向网络功能管理器(x network function manager,xNFM)下达创建针对VNF及PNF的PM管理任务的请求。xNFM直接建立针对VNF的PM管理任务,xNFM向EMS下发创建针对PNF的PM管理任务的请求,EMS建立针对PNF的PM管理任务。
上述两种创建PM管理任务的方案是出于不同的PM管理目的,两种方案均通过EMS收集PNF的性能信息,分别从针对NE、NS实例的性能管理需求出发创建PM管理任务。当两种方案针对同一个PNF搜集相同的性能指标时,则会通过EMS分别创建了两个管理任务,这两个PM管理任务的对象均为PNF且搜集的性能数据相同,两个体系在EMS创建了重复的PM管理任务,导致EMS在进行性能管理时需要处理冗余建立PM管理任务,管理效率不高。
发明内容
本申请实施例提供一种创建PM任务的方法及装置,以实现高效的PM任务管理。
为达到上述目的,本申请实施例采用如下技术方案:
第一方面,提供一种创建PM任务的方法,该方法可以包括:PM任务管理器获取第一信息及混合NS的ID,第一信息包括该混合NS中的PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息、上报周期的信息,第一信息用于指示创建按照第一信息中的收集周期搜集第一信息中的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任务;PM任务管理器向EMS发送第一信息;PM任务管理器从EMS接收第一PM任务的ID;PM任务管理器向EMS发送第一PM任务的ID、该混合NS的ID以及订阅标识,订阅标识用于针对该混合NS订阅第一PM任务。
通过本申请提供的创建PM任务的方法,在创建针对PNF的PM任务时,PM任务管理器向EMS查询是否已存在重复的第一PM任务,并在存在第一PM任务时向EMS订阅第一PM任务,避免EMS在进行性能管理时建立冗余重复的PM管理任务,提高了管理效率。
其中,第一信息及混合NS的ID可以携带在第一创建请求中,第一创建请求用于请求建立其包括的信息指示的PM任务,第一创建请求包括的信息指示的PM任务,是按照第一创建请求包括的收集周期,搜集第一创建请求包括的PNF的一个或多个性能指标,并按照第一创建请求包括的上报周期信息上报搜集的性能指标的PM任务。
需要说明的是,第一PM任务与第一信息指示的PM任务功能重叠。本文所称的功能重叠,是指两个PM任务的管理对象相同、搜集的性能指标相同、PM搜集频率和上报频率相同。相互重叠的PM任务的生命周期可以相同,也可以不同,本申请对此不进行具体限定。
其中,第一PM任务的ID、该混合NS的ID以及订阅标识可以携带在订阅请求中,通过订阅标识标记该请求为订阅请求。
结合第一方面,在一种可能的实现方式中,本申请提供的创建PM任务的方法还可以包括:PM任务管理器未接收到第一PM任务的ID,PM任务管理器可以向EMS发送第一信息以及混合NS的ID,用于EMS创建第二PM任务。在创建针对PNF的PM任务时,若PM任务管理器向EMS查询不存在重复的第一PM任务,则创建第一创建请求包括的信息指示的PM任务,避免EMS在进行性能管理时建立冗余重复的PM管理任务,提高了管理效率。其中,第一信息以及混合NS的ID可以携带在第二创建请求中。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的创建PM任务的方法还可以包括:PM任务管理器将混合NS的ID与第一PM任务的ID对应记录,并标记第一PM任务的状态为订阅。以便于后续查询不同的PM任务的状态是订阅还是新建。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的创建PM任务的方法还可以包括:PM任务管理器从EMS接收PM任务创建响应,PM任务创建响应包括第二PM任务的标识;PM任务管理器将混合NS的ID与 第二PM任务的ID对应记录,并标记第二PM任务的状态为新建。以便于后续查询不同的PM任务的状态是订阅还是新建。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,PM任务管理器获取第一信息及混合NS的ID,具体可以实现为:PM任务管理器从NM接收第一信息及混合NS的ID;或者,PM任务管理器从NFVO接收第一信息及混合NS的ID;或者,PM任务管理器从xNFM接收第一信息及混合NS的ID。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,PM任务管理器可以作为一个功能模块部署于NM中,PM任务管理器从NM内部接收第一信息及混合NS的ID。在该实现方式中,NM将针对该混合NS的PM任务创建请求,拆分为针对该混合NS中VNF的PM任务以及针对该混合NS中PNF的PM任务的创建请求,将针对该混合NS中VNF的PM任务的创建请求通过NFVO发送给xNFM;将针对该混合NS中PNF的PM任务的创建请求(包括第一信息及混合NS的ID)发送给内部的PM任务管理器。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,PM任务管理器可以作为一个功能模块部署于xNFM中,PM任务管理器则从NFVO接收第一信息及混合NS的ID。在该实现方式中,NFVO从NM接收针对该混合NS的PM任务创建请求,由NFVO拆分为针对该混合NS中VNF的PM任务以及针对该混合NS中PNF的PM任务的创建请求(包括第一信息及混合NS的ID),并发送给xNFM,部署于xNFM中PM任务管理器则从NFVO接收第一信息及混合NS的ID。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,PM任务管理器可以作为一个单独的模块部署于EMS与xNFM之间,PM任务管理器则从xNFM接收第一信息及混合NS的ID。在该实现方式中,NFVO从NM接收针对该混合NS的PM任务创建请求,由NFVO拆分为针对该混合NS中VNF的PM任务以及针对该混合NS中PNF的PM任务的创建请求(包括第一信息及混合NS的ID),并发送给xNFM;xNFM负责创建针对该混合NS中VNF的PM任务,以及向PM任务管理器发送针对该混合NS中PNF的PM任务的创建请求(包括第一信息及混合NS的ID),部署于EMS与xNFM之间的PM任务管理器则从xNFM接收第一信息及混合NS的ID。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的创建PM任务的方法还可以包括:PM任务管理器接收第三PM任务的ID、混合NS的ID及删除标识,该删除标识用于指示删除针对混合NS的第三PM任务;若不存在该混合NS之外的其他网元使用第三PM任务,PM任务管理器通过EMS删除第三PM任务,并删除记录的第三PM任务与混合NS的ID的对应关系。若第三PM任务为订阅,且存在该混合NS之外的其他网元使用第三PM任务,PM任务管理器取消订阅第三PM任务,并删除记录的第三PM任务与混合NS的ID的对应关系。若第三PM任务为新建,且存在混合NS之外的其他网元使用第三PM任务,删除记录的第三PM任务与混合NS的ID的对应关系。
其中,第三PM任务的ID、混合NS的ID及删除标识可以携带在删除请求中,通过删除标识标记该请求为删除请求。
第二方面,提供另一种创建PM任务的方法,该方法可以包括:EMS从PM任务管理器接收第一信息,第一信息包括PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息、上报周期的信息;EMS确定存在第一PM任务,第一PM任务是按照第一信息中的收集周期,搜集第一信息中的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任务;EMS向PM任务管理器发送第一PM任务的标识ID;EMS从PM任务管理器接收第一PM任务的ID、混合NS的ID以及订阅标识,订阅标识用于针对混合NS订阅第一PM任务。
通过本申请提供的创建PM任务的方法,在创建针对PNF的PM任务时,PM任务管理器向EMS查询是否已存在重复的第一PM任务,并在存在第一PM任务时向EMS订阅第一PM任务,避免EMS在进行性能管理时建立冗余重复的PM管理任务,提高了管理效率。
结合第二方面,本申请提供的创建PM任务的方法还可以包括:EMS在执行第一PM任务后,按照上报周期信息,向PM任务管理器上报针对该混合NS搜集的PNF的一个或多个性能指标。或者,EMS在执行第一PM任务后,按照上报周期信息,向NM上报针对该混合NS搜集的PNF的一个或多个性能指标。
结合第二方面或上述任一种可能的实现方式,本申请提供的创建PM任务的方法还可以包括:若不存在第一PM任务,EMS从PM任务管理器接收第一信息以及混合NS的ID;EMS创建第二PM任务,第二PM任务是第一信息指示的PM任务;EMS向PM管理器发送PM任务创建响应,该PM任务创建响应包括第二PM任务的标识。
结合第二方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的创建PM任务的方法还可以包括:EMS从PM任务管理器接收第三PM任务的ID、混合NS的ID及取消订阅标识;EMS在执行第三PM任务后,停止上报针对该混合NS搜集的所述第三PM任务的性能指标。
其中,第三PM任务的ID、混合NS的ID及取消订阅标识可以携带在取消订阅请求中,通过取消订阅标识标记该请求为取消订阅请求。
结合第二方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的创建PM任务的方法还可以包括:EMS从PM任务管理器接收第三PM任务的ID、混合NS的ID及删除标识;EMS删除第三PM任务。
其中,第三PM任务的ID、混合NS的ID及删除标识可以携带在删除请求中,通过删除标识标记该请求为删除请求。
第三方面,提供一种创建PM任务的装置,该装置可以是PM任务管理器,PM任务管理器可以部署于NM内部或者xNFM内部,或者部署于xNFM与EMS之间。该装置可以为芯片***。该装置可以实现上述各方面或者各可能的设计中PM任务管理器所执行的功能,所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如:该创建PM任务的装置可以包括:获取单元、发送单元及接收单元。
其中,获取单元,用于获取第一信息及NS的标识ID,第一信息包括NS中的物理网络功能PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息、上报周期的信息;第一信息用于指示创建按照第一信息中的收集周期,搜集第一信息中 的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任务。
发送单元,用于向EMS发送第一信息。
接收单元,用于从EMS接收第一PM任务的ID,第一PM任务是按照第一信息中的收集周期,搜集第一信息中的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任务。
发送单元还用于,向EMS发送第一PM任务的ID、混合NS的ID及订阅标识,订阅标识用于针对该混合NS订阅所述第一PM任务。
需要说明的是,第三方面提供的创建PM任务的装置,用于执行上述第一方面提供的创建PM任务的方法,具体实现可以参考上述第一方面的具体实现。
第四方面,提供另一种创建PM任务的装置,该装置可以是EMS,或者可以是部署于EMS中的装置或者芯片***。该装置可以实现上述各方面或者各可能的设计中EMS所执行的功能,所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如:该创建PM任务的装置可以包括:接收单元、判断单元及发送单元。
其中,接收单元,用于从PM任务管理器接收第一信息,第一信息包括PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息、上报周期的信息。
确定单元,用于确定存在第一PM任务,第一PM任务是按照第一信息中的收集周期,搜集第一信息中的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任务。
发送单元,用于向PM任务管理器发送第一PM任务的标识ID。
接收单元还用于,从PM任务管理器接收第一PM任务的ID、混合NS的ID以及订阅标识,订阅标识用于针对混合NS订阅所述第一PM任务。
需要说明的是,第四方面提供的创建PM任务的装置,用于执行上述第二方面提供的创建PM任务的方法,具体实现可以参考上述第二方面的具体实现。
第五方面,本申请提供一种PM任务管理器,该PM任务管理器可以包括:处理器,存储器;处理器,存储器耦合,存储器可用于存储计算机程序代码,计算机程序代码包括计算机指令,当计算机指令被PM任务管理器执行时,使得PM任务管理器执行如第一方面或任一种可能的实现方式面所述的创建PM任务的方法。
第六方面,本申请提供一种EMS,该EMS可以包括:处理器,存储器;处理器,存储器耦合,存储器可用于存储计算机程序代码,计算机程序代码包括计算机指令,当计算机指令被EMS执行时,使得EMS执行如第二方面或任一种可能的实现方式面所述的创建PM任务的方法。
第七方面,本申请提供一种计算机可读存储介质,该计算机可读存储介质可以包括:计算机软件指令;当计算机软件指令在PM任务管理器中运行时,使得该PM任务管理器执行如第一方面或第一方面的可能实现方式中任一项所述的创建PM任务的方法。
第八方面,本申请提供一种计算机可读存储介质,该计算机可读存储介质可以包括:计算机软件指令;当计算机软件指令在EMS中运行时,使得该EMS执行如第二 方面或第二方面的可能实现方式中任一项所述的创建PM任务的方法。
第九方面,本申请提供一种计算机程序产品,当该计算机程序产品在计算机上运行时,使得该计算机执行如权利要求第一方面或或第二方面或任一种可能的实现方式中任一项所述的创建PM任务的方法。
第十方面,本申请提供一种芯片***,该芯片***应用于PM任务管理器或者EMS;该芯片***包括接口电路和处理器;接口电路和处理器通过线路互联;接口电路用于从PM任务管理器或者EMS的存储器接收信号,并向处理器发送信号,信号包括存储器中存储的计算机指令;当处理器执行该计算机指令时,芯片***执行如第一方面或第二方面或任一种可能的实现方式中任一项所述的创建PM任务的方法。
第十一方面,本申请提供一种PM管理***,包括PM任务管理器及EMS,PM任务管理器执行如第一方面或第一方面的可能实现方式中任一项所述的创建PM任务的方法,EMS执行如第二方面或第二方面的可能实现方式中任一项所述的创建PM任务的方法。
应当理解的是,本申请中对技术特征、技术方案、有益效果或类似语言的描述并不是暗示在任意的单个实施例中可以实现所有的特点和优点。相反,可以理解的是对于特征或有益效果的描述意味着在至少一个实施例中包括特定的技术特征、技术方案或有益效果。因此,本说明书中对于技术特征、技术方案或有益效果的描述并不一定是指相同的实施例。进而,还可以任何适当的方式组合本实施例中所描述的技术特征、技术方案和有益效果。本领域技术人员将会理解,无需特定实施例的一个或多个特定的技术特征、技术方案或有益效果即可实现实施例。在其他实施例中,还可在没有体现所有实施例的特定实施例中识别出额外的技术特征和有益效果。
图1为一种PM管理场景的示意图;
图2为ETSI中的PM管理的过程的流程示意图;
图3为本申请实施例提供的一种PM管理***框架的结构示意图;
图4为本申请实施例提供的一种通信装置的结构示意图;
图5为本申请实施例提供的一种创建PM任务的方法的流程示意图;
图6为本申请实施例提供的另一种创建PM任务的方法的流程示意图;
图7为本申请实施例提供的一种创建PM任务的装置的结构示意图;
图8为本申请实施例提供的另一种创建PM任务的装置的结构示意图;
图9为本申请实施例提供的再一种创建PM任务的装置的结构示意图;
图10为本申请实施例提供的又一种创建PM任务的装置的结构示意图。
在本申请实施例中,为了便于清楚描述本申请实施例的技术方案,采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定,并且“第一”、“第二”等字样也并不限定一定不同。该“第一”、第二”描述的技术特征间无先后顺序或者大小顺序。
在本申请实施例中,“示例性的”或者“例如”等词用于表示作例子、例证或说明。 本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言,使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念,便于理解。
在本申请的描述中,除非另有说明,“/”表示前后关联的对象是一种“或”的关系,例如,A/B可以表示A或B;本申请中的“和/或”仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况,其中A,B可以是单数或者复数。并且,在本申请的描述中,除非另有说明,“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达,是指的这些项中的任意组合,包括单项(个)或复数项(个)的任意组合。例如,a,b,或c中的至少一项(个),可以表示:a,b,c,a-b,a-c,b-c,或a-b-c,其中a,b,c可以是单个,也可以是多个。
在本申请实施例中,至少一个还可以描述为一个或多个,多个可以是两个、三个、四个或者更多个,本申请不做限制。
需要说明的是,本申请中描述的A向B发送某内容,当网络架构中A和B之间不是直连时,可通过A和B之间的网元逐级转发该内容,使得该内容到达B,本文中统一描述为“A向B发送该内容”。
还需要说明的是,本申请中描述的请求、消息或者信息的名称,均为示例性描述,具体实现中请求、消息或者信息的名字可以为其他,本申请实施例对此不作具体限定。
此外,本申请实施例描述的网络架构以及场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
在介绍本申请的具体实现之前,此处先对本申请涉及的名词进行解释。
功能重叠的PM任务,是指两个PM任务的管理对象相同、搜集的性能指标重叠、PM搜集频率和上报频率相同。其中,搜集的性能指标重叠包括搜集的性能指标相同、搜集的性能指标可相互转换等。相互重叠的PM任务的生命周期可以相同,也可以不同。
随着NFV技术的发展,通信***的物理网元可以采用NFV技术虚拟化为VNF,当然,也存在部分无法虚拟化的物理网元(PNF),这样就形成了混合NS。网络的运行过程中,需要进行PM管理。PM管理通常先创建PM管理任务(PM Job),通过执行PM管理任务搜集NS中VNF、PNF的性能指标进行网络运维。在描述本申请实施例之前,先对ETSI中的PM管理的过程进行简单描述。NM在有PM管理需求时,触发启动该PM管理过程。PM管理需求可以根据***管理员的配置进行,本申请实施例对此不进行具体限定。
ETSI中的PM管理的过程可以参照协议GS-IFA010。如图2所示,ETSI中的PM管理的过程可以包括:
S201、NM向NFVO发送PM任务创建请求。
其中,该PM任务创建请求可以包括:NS标识、一个或多个性能指标的信息、收集周期的信息、上报周期的信息以及生命周期信息。
示例性的,该PM任务创建请求中包括的参数可以如表1所示。
表1
S202、NFVO创建针对NS的PM任务的ID。
S203、NFVO向NM发送PM任务建立响应消息。
其中,PM任务建立响应消息中包括NFVO创建的针对NS的PM任务的ID。
S204、NFVO将针对NS的PM任务,拆分成针对VNF和PNF的PM任务。
其中,NFVO中记录了不同NS中包括的VNF和PNF,S204根据记录的NS中包括的VNF和PNF,将将针对NS的PM任务,拆分成针对VNF和PNF的PM任务。
S205、NFVO向xNFM发送PM任务创建请求。
其中,S205中的PM任务创建请求的数据,与NS中包括的VNF和PNF总量相同,即S205中NFVO针对NS中的每个VNF和PNF分别发送一个PM任务创建请求。
具体的,该PM任务创建请求中包括VNF或者PNF的标识、一个或多个性能指标的信息、收集周期的信息、上报周期的信息以及生命周期信息。
S206、xNFM创建针对VNF的PM任务并执行针对VNF的PM任务。
其中,执行针对VNF的PM任务,即在针对VNF的PM任务的生命周期中,按照收集周期收集一个或多个性能指标的性能信息,并按照上报周期通过NFVO向NM上报收集的性能信息。
S207、xNFM向EMS发送针对PNF的PM任务创建请求。
具体的,该PM任务创建请求中包括PNF的标识、一个或多个性能指标的信息、收集周期的信息、上报周期的信息以及NS标识。
S208、EMS创建针对PNF的PM任务并执行针对VNF的PM任务。
其中,执行针对PNF的PM任务,即在针对PNF的PM任务的生命周期中,按照收集周期收集一个或多个性能指标的性能信息,并按照上报周期通过xNFM、NFVO向NM上报收集的性能信息。
如前所述,3GPP提供了一种针对NE创建PM管理任务的方案,NM向EMS下达针对NE创建PM管理任务的请求,EMS根据NM的请求内容,建立针对该NE的PM管理任务并执行,与ETSI提供的方案均通过EMS收集PNF的性能信息,可能会出现两个体系在EMS创建了重复的PM管理任务的情况,造成EMS在进行性能管理 时需要处理冗余建立PM管理任务,管理效率不高。
基于此,本申请提供的方案的基本原理为:PM任务管理器在接收到新的创建PM任务请求时,先确认请求创建的PM任务是否与已经存在的PM任务功能重叠,若重叠则直接订阅无需新创建,避免EMS在进行性能管理时建立冗余重复的PM管理任务,提高了管理效率。
本申请提供的方案,可以应用于图3示意的PM管理***的框架,该框架可以应用于任一通信***。该通信***可以为第三代合作伙伴计划(3rd generation partnership project,3GPP)通信***,例如,长期演进(long term evolution,LTE)***,又可以为第五代移动通信***(the 5th,5G)或者新空口(new radio,NR)***,也可以为非3GPP通信***,不予限制。
如图3所示,该PM管理***包括NM 301、NFVO 302、xNFM 303、PM任务管理器304以及EMS 305。该PM管理***用于管理NS 306,如图3所示,NS 306包括PNF 3061以及VNF 3062。
其中,PM任务管理器304是本申请的核心网元,负责查询和管理已经存在的PM Job,当接收到新的创建PM Job请求时,首先确认新创建的PM Job是否与已经存在的PM Job功能重叠。如图3所示,PM任务管理器304可以作为功能网元部署于NM 301内部(图3中位置1),或者作为功能网元部署于xNFM 303内部(图3中位置2),或者作为单独模块部署于xNFM 303与EMS 305之间(图3中位置3)。
NM 301是电信运营商的一体化、信息资源共享的支持***,它主要由网络管理、***管理、计费、营业、账务和客户服务等部分组成,***间通过统一的信息总线有机整合在一起,向NFVO 302发送针对NS 206实例的PM管理请求。NM 301可以为运营支撑***(operation support system,OSS)/业务支撑***(business support system,BSS)。
NFVO 302负责创建针对整个NS 306实例的PM Job,将针对NS 306实例的PM管理需求分解为针对NS 306实例中PNF 3061和VNF 3062的管理需求,并向xNFM 303下发。
xNFM 303负责根据NFVO 302的需求,创建针对VNF 3062的PM Job,根据NFVO 302下发的需求,通过EMS 305创建针对PNF 3061的PM Job。
EMS 305是管理特定类型的一个或多个电信网络单元的***,由各个公司单独开发,负责管理各个公司的PNF和VNF,根据需求创建PM Job,并搜集PNF对应的信息。
需要指出的是,本申请实施例所应用的PM管理***的架构不限定图3所示的网络架构。此外,图3所示PM管理***的架构仅为示例性架构图,PM管理***包括的网元的数量以及网元名称均不做限定。例如,除图3所示网元外,图3所示PM管理***还可以包括其他网元。再例如,上述图3架构中的网元、各个网元的名字只是一个示例,具体实现中网元的名字可以为其他,本申请实施例对此不作具体限定。
下面将结合附图对本申请实施例的实施方式进行详细描述。需要指出的是,本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例,具体实现中也可以是其他的名字,本申请实施例对此不作具体限定。
图4为本申请实施例提供的一种通信装置40的组成示意图,如图4所示,该通信装置40可以包括至少一个处理器41,存储器42、通信接口43、通信总线44。下面结合图4对通信装置40的各个构成部件进行具体的介绍:
处理器41,可以是一个处理器,也可以是多个处理元件的统称。例如,处理器41是一个中央处理器(central processing unit,CPU),也可以是特定集成电路(application specific integrated circuit,ASIC),或者是被配置成实施本申请实施例的一个或多个集成电路,例如:一个或多个微处理器(digital signal processor,DSP),或,一个或者多个现场可编程门阵列(field programmable gate array,FPGA)。
其中,处理器41可以通过运行或执行存储在存储器42内的软件程序,以及调用存储在存储器42内的数据,执行功能别名控制服务器的各种功能。在具体的实现中,作为一种实施例,处理器41可以包括一个或多个CPU,例如图4中所示的CPU0和CPU1。
在具体实现中,作为一种实施例,该通信装置40可以包括多个处理器,例如图4中所示的处理器41和处理器45。这些处理器中的每一个可以是一个单核处理器(single-CPU),也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器42可以是只读存储器(read-only memory,ROM)或可存储静态信息和指令的其他类型的静态存储设备,随机存取存储器(random access memory,RAM)或者可存储信息和指令的其他类型的动态存储设备,也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory,EEPROM)、只读光盘(compact disc read-only memory,CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器42可以是独立存在,通过通信总线44与处理器41相连接。存储器42也可以和处理器41集成在一起。其中,存储器42用于存储执行本申请方案的软件程序,并由处理器41来控制执行。
通信接口43,使用任何收发器一类的装置,用于与其他设备或通信网络通信,如以太网,无线接入网(radio access network,RAN),无线局域网(wireless local area networks,WLAN)等。通信接口43可以包括接收单元以及发送单元。
通信总线44,可以是工业标准体系结构(industry standard architecture,ISA)总线、外部设备互连(peripheral component,PCI)总线或扩展工业标准体系结构(extended industry standard architecture,EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示,图4中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
需要指出的是,图4中示出的部件并不构成对该通信装置的限定,除图4所示部件之外,该通信装置可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
一种可能的实现中,通信装置40可以作为PM任务管理器,处理器41通过运行或执行存储在存储器42内的软件程序和/或模块,以及调用存储在存储器42内的数据, 执行如下功能:
获取第一信息及混合NS的ID,第一信息包括该混合NS中PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息以及上报周期的信息;通过通信接口43向EMS发送第一信息;通过通信接口43从EMS接收第一PM任务的标识ID,通过通信接口43向EMS发送第一PM任务的ID、混合NS的ID及订阅标识,订阅标识用于针对所述混合NS订阅所述第一PM任务。其中,第一PM任务是按照第一信息中的收集周期,搜集第一信息中的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任务。
另一种可能的实现中,通信装置40可以作为EMS,处理器41通过运行或执行存储在存储器42内的软件程序和/或模块,以及调用存储在存储器42内的数据,执行如下功能:
通过通信接口43从PM任务管理器接收第一信息,第一信息包括PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息、上报周期的信息;确定存在第一PM任务,第一PM任务是按照第一信息中的收集周期,搜集第一信息中的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任务;通过通信接口43向PM任务管理器发送第一PM任务的标识ID。从PM任务管理器接收第一PM任务的ID、混合NS的ID以及订阅标识,订阅标识用于针对该混合NS订阅所述第一PM任务。
一方面,本申请实施例提供一种创建PM任务的方法,应用于PM管理过程中。NM在有PM管理需求时,触发启动PM管理过程,本申请提供的方案是在将针对NS的PM任务,拆分成针对该NS中的VNF和PNF的PM任务之后,对针对PNF的PM任务的创建,对于针对NS中的VNF的PM任务的创建即执行,参照前述图2示意的PM管理过程中的相关内容即可,本申请不再进行赘述。
如图5所示,本申请实施例提供的创建PM任务的方法可以包括:
S501、PM任务管理器获取第一信息及混合NS的ID。
其中,第一信息及混合NS的ID可以携带于针对混合NS中PNF的第一创建请求中。
其中,第一信息用于请求创建第一信息指示的PM任务。第一信息指示的PM任务,是按照第一信息中的收集周期,搜集第一信息中的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任务。
具体的,根据PM任务管理器在PM管理***中的部署位置不同,S501中PM任务管理器获取第一信息及混合NS的ID的方式也不同,包括但不限于下述三种可能的实现:
实现1、PM任务管理器从NM接收第一信息及混合NS的ID。
在实现1中,PM任务管理器可以作为一个功能模块部署于NM中,PM任务管理器从NM内部接收第一信息及混合NS的ID。在该实现方式中,NM将针对该混合NS的PM任务创建请求,拆分为针对该混合NS中VNF的PM任务以及针对该混合NS中PNF的PM任务的创建请求(包括第一信息及混合NS的ID),将针对该混合NS中VNF的PM任务的创建请求通过NFVO发送给xNFM;将针对该混合NS中PNF 的PM任务的创建请求(包括第一信息及混合NS的ID)发送给内部的PM任务管理器。
其中,NM将针对该混合NS的PM任务创建请求,拆分为针对该混合NS中VNF的PM任务以及针对该混合NS中PNF的PM任务的创建请求可以与S204中的NFVO相同,此处不再进行赘述。
实现2、PM任务管理器从NFVO接收第一信息及混合NS的ID。
在实现2中,PM任务管理器可以作为一个功能模块部署于xNFM中,NFVO从NM接收针对该混合NS的PM任务创建请求(与前述S201相同),由NFVO拆分为针对该混合NS中VNF的PM任务以及针对该混合NS中PNF的PM任务的创建请求(与前述S204相同,包括第一信息及混合NS的ID),并发送给xNFM(与前述S205相同),部署于xNFM中PM任务管理器则从NFVO接收包括第一信息及混合NS的ID。
实现3、PM任务管理器从xNFM接收包括第一信息及混合NS的ID。
在实现3中,PM任务管理器可以作为一个单独的模块部署于EMS与xNFM之间,NFVO从NM接收针对该混合NS的PM任务创建请求(与前述S201相同),由NFVO拆分为针对该混合NS中VNF的PM任务以及针对该混合NS中PNF的PM任务的创建请求(与前述S204相同,包括第一信息及混合NS的ID),并发送给xNFM(与前述S205相同);xNFM负责创建针对该混合NS中VNF的PM任务,以及向PM任务管理器发送针对该混合NS中PNF的PM任务的创建请求(包括第一信息及混合NS的ID),部署于EMS与xNFM之间的PM任务管理器则从xNFM接收包括第一信息及混合NS的ID。
S502、PM任务管理器向EMS发送第一信息。
其中,在S502中,第一信息可以携带于PM任务匹配请求中发送,S502中发送的第一信息用于请求EMS判断是否存在已经建立的,与第一信息指示的PM任务功能重叠的PM任务。
一种可能的实现中,S502中在向EMS发送第一信息时,可以携带匹配标识,用于指示发送的第一信息用于请求EMS判断是否存在已经建立的,与第一信息指示的PM任务功能重叠的PM任务。
需要说明的是,S502中发送的第一信息,可以与S501中获取的第一信息完全相同,也可以是S501中获取的第一信息中包括的性能指标转换后的第一信息,本申请实施例对此不进行具体限定。
S503、EMS从PM任务管理器接收第一信息。
其中,S503中EMS接收的第一信息,即为S502中PM任务管理器发送的,此处不再赘述。
在S503之后,EMS判断是否存在第一PM任务。
具体的,EMS中记录了已经建立的每个PM任务的信息,在S504中,EMS根据记录的信息判断是否存在第一PM任务。
其中,第一PM任务是按照第一信息中的收集周期,搜集第一信息中的PNF的一个或多个性能指标,并按照第一信息中的上报周期信息上报搜集的性能指标的PM任 务。也即,第一PM任务与第一信息指示的PM任务功能重叠。
需要说明的是,第一PM任务的生命周期可以与第一信息指示的PM任务的生命周期相同或者不同。
S504、EMS确定是否存在第一PM任务。
进一步的,在S504中,当EMS确定存在第一PM任务,且第一PM任务的生命周期早于第一信息指示的PM任务的生命周期的边界时间时,EMS还需修改第一PM任务的生命周期,将第一信息指示的PM任务的生命周期的边界时间作为第一PM任务的生命周期的边界时间。
S505、EMS向PM任务管理器发送第一PM任务的ID。
其中,在S505中,第一PM任务的ID可以携带于PM任务匹配响应。
S506、PM任务管理器从EMS接收第一PM任务的ID。
S507、PM任务管理器向EMS发送第一PM任务的ID、混合NS的ID及订阅标识。
其中,S507中发送的混合NS的ID为S501中获取的混合NS的ID。
具体的,S507中,第一PM任务的ID、该混合NS的ID以及订阅标识可以携带在订阅请求中,通过订阅标识标记该请求为订阅请求。
S507的操作用于向EMS订阅第一PM任务,使得EMS在执行第一PM任务后,按照第一PM任务的上报周期,上报执行第一PM任务搜集的性能信息,作为针对该混合NS的PM管理数据。
S508、EMS从PM任务管理器接收第一PM任务的ID、混合NS的ID及订阅标识。
其中,S508中EMS接收的第一PM任务的ID、混合NS的ID及订阅标识,即为S507中PM任务管理器发送的第一PM任务的ID、混合NS的ID及订阅标识,此处不再赘述。
到S508则通过订阅已有的PM任务的方式,避免了在EMS建立重复的PM任务。EMS在执行第一PM任务后,则按照第一PM任务的上报周期,上报执行第一PM任务搜集的性能信息,作为针对该订阅请求中包括的混合NS的PM管理数据。
通过本申请提供的创建PM任务的方法,在创建针对PNF的PM任务时,PM任务管理器向EMS查询是否已存在重复的第一PM任务,并在存在第一PM任务时向EMS订阅第一PM任务,避免EMS在进行性能管理时建立冗余重复的PM管理任务,提高了管理效率。
进一步的,如图6所示,在S508之后,本申请实施例提供的创建PM任务的方法还可以包括S509。
S509、EMS在执行第一PM任务后,按照第一PM任务的上报周期,上报搜集的第一PM任务的性能指标。
一种可能的实现中,在S509中,EMS在执行第一PM任务后,按照第一PM任务的上报周期,向PM任务管理器上报搜集的第一PM任务的性能指标,上报的性能指标作为针对第一创建请求中包括的混合NS的PNF的性能报告,以管理第一创建请求中包括的混合NS。
例如,在S509中,EMS在执行第一PM任务后,按照第一PM任务的上报周期,向PM任务管理器上报搜集的第一PM任务的性能指标,当PM任务管理器部署于xNFM或者xNFM与EMS之间时,由NFVO将针对PNF的性能报告,与xNFM搜集的针对VNF的性能报告合并为针对混合NS的性能报告发送个NM。
另一种可能的实现中,在S509中,EMS在执行第一PM任务后,按照第一PM任务的上报周期,向网络管理器NM上报搜集的第一PM任务的性能指标,上报的性能指标作为针对第一创建请求中包括的混合NS的PNF的性能报告,以管理该混合NS。
例如,在S509中,EMS在执行第一PM任务后,按照第一PM任务的上报周期,向NM上报搜集的第一PM任务的性能指标,上报的性能指标作为针对第一创建请求中包括的混合NS的PNF的性能报告,由NM将针对PNF的性能报告,与xNFM搜集的针对VNF的性能报告合并为针对混合NS的性能报告。
进一步的,如图6所示,在S507之后,本申请实施例提供的创建PM任务的方法还可以包括S510。
S510、PM任务管理器将混合NS的ID与第一PM任务的ID对应记录,并标记第一PM任务的状态为订阅。
通过S510记录了第一PM任务为订阅状态,便于后续取消订阅或者删除。
进一步的,若S503中判断不存在第一PM任务,如图6所示,本申请实施例提供的创建PM任务的方法还可以包括S511-S516。
S511、PM任务管理器向EMS发送第一信息及混合NS的ID。
其中,S511中发送的第一信息以及混合NS的ID可以携带在第二创建请求中。
S511的操作用于请求EMS创建第二PM任务,第二PM任务就是第一信息信息指示的PM任务。
进一步的,S511中发送第一信息及混合NS的ID时,还可以携带创建标识,创建标识以指示用于请求EMS创建第二PM任务。
需要说明的是,S511中发送的第一信息,可以与S501中获取的第一信息完全相同,也可以是S501中获取的第一信息中包括的性能指标转换后的第一信息,本申请实施例对此不进行具体限定。
S512、EMS从PM任务管理器接收第一信息及混合NS的ID。
其中,S512中EMS接收的第一信息及混合NS的ID,即为S511中PM任务管理器发送的第一信息及混合NS的ID,此处不再赘述。
S513、EMS创建第二PM任务。
具体的,S513中EMS创建PM任务的过程,可以参照协议3GPP 32412,本申请实施例对此不进行具体赘述。
S514、EMS向PM任务管理器发送PM任务创建响应。
其中,PM任务创建响应包括第二PM任务的标识,PM任务创建响应用于通知PM任务管理器,已完成第二PM任务的建立。
S515、PM任务管理器从EMS接收PM任务创建响应。
其中,S515中PM任务管理器接收的PM任务创建响应,即为S514中EMS发送的PM任务创建响应,此处不再赘述。
S516、PM任务管理器将该混合NS的ID与第二PM任务的ID对应记录,并标记第二PM任务的状态为新建。
通过S516记录了第二PM任务为订阅状态,便于后续取消订阅或者删除。
示例性的,通过上述S510及S516的过程,PM任务管理器可以记录了如表2示意的状态信息。状态信息中记录了针对不同NS的不同PM任务的状态,便于后续取消订阅或者删除。
表2
需要说明的是,表2示意的状态信息仅为举例说明,并不是对状态信息的内容以及形式的具体限定。
上述过程描述了PM管理过程中,根据PM管理需求订阅或者创建PM任务的过程。相应的,在PM管理过程中,根据PM管理需求还需要删除一些正在执行的PM任务,下面对于PM任务的删除过程进行说明。如图6所示,PM任务的删除过程可以包括S517-S523中的部分或全部。
进一步的,在PM过程中,还需要删除一些PM任务,此时,以删除第三PM任务为例进行说明,该方法还包括:
S517、PM任务管理器接收第三PM任务的ID、混合NS的ID及删除标识。
其中,第三PM任务的ID、混合NS的ID及删除标识可以携带在删除请求中,通过删除标识标记该请求为删除请求。删除标识用于指示删除针对该混合NS的第三PM任务。第三PM任务为EMS执行的PM任务中的任一个。
需要说明的是,PM任务管理器接收第三PM任务的ID、混合NS的ID及删除标识的方式,与S501中PM任务管理器接收第一信息及混合NS的ID的方式相似,此处不再赘述。
具体的,在S517中接收到删除请求之后,根据记录的针对删除请求中包括的混合NS的第三PM任务的状态具体执行删除操作。示例性的,PM任务管理器在S517中接收到删除请求之后,可以查询如表2示意的状态信息中,针对删除请求中包括的混合NS的第三PM任务的状态选择后续不同的实现执行删除操作。
一种可能的实现中,若不存在删除请求中的混合NS之外的其他网元使用第三PM任务,则执行S518和S519删除第三PM任务。该可能的实现中,无论第三PM任务为订阅还是新建,均执行S518和S519删除第三PM任务。
S518、PM任务管理器通过EMS删除第三PM任务,并删除记录的第三PM任务与混合NS的ID的对应关系。
具体的,在S518中,PM任务管理器向EMS发送删除请求,该删除请求包括第 三PM任务的ID,用于指示EMS删除第三PM任务。
S519、EMS删除第三PM任务。
通过S518和S519,EMS将第三PM任务进行了删除,之后不再执行第三PM任务。
另一种可能的实现中,若第三PM任务为订阅,且存在删除请求中的混合NS之外的其他网元使用第三PM任务,执行S520-S522。
S520、PM任务管理器取消订阅第三PM任务,并删除记录的第三PM任务与混合NS的ID的对应关系。
具体的,在S520中,PM任务管理器向EMS发送第三PM任务的ID、混合NS的ID及取消订阅标识,用于指示EMS不再上报针对该混合NS的PNF的第三PM任务的性能报告。
其中,第三PM任务的ID、混合NS的ID及取消订阅标识可以携带在取消订阅请求中,通过取消订阅标识标记该请求为取消订阅请求。
S521、EMS从PM任务管理器接收第三PM任务的ID、混合NS的ID及取消订阅标识。
S522、EMS在执行第三PM任务后,停止上报针对取消订阅请求中包括的混合NS搜集的第三PM任务的性能指标。
通过S520-S522,PM任务管理器向EMS取消订阅了第三PM任务,之后EMS执行第三PM任务后,不再上报针对取消订阅请求中包括的混合NS的第三PM任务的性能指标,但还会上报针对其他使用第三PM任务的网元的第三PM任务的性能指标。
再一种可能的实现中,若第三PM任务为新建,且存在删除请求中的混合NS之外的其他网元使用第三PM任务,执行S523。
S523、PM任务管理器删除记录的第三PM任务与混合NS的ID的对应关系。
通过S523,PM任务管理器仅需删除内部记录的第三PM任务与S517中的删除请求中包括的混合NS的ID的对应关系即可,无需与EMS交互任何信息。
在上述S518和S519,或者S520-S522,或者S523之后,PM任务管理器还需反馈S517中的删除请求的响应消息,用于通知第三PM任务已完成删除。
需要说明的是,本申请实施例中提供的创建PM任务的方法中包括的步骤的执行顺序,可以根据实际需求配置,本申请实施例对此不进行具体限定,图5及图6中仅示意了一种可能的执行顺序,并不够成具体限定。
上述主要从PM任务管理器与EMS工作原理的角度对本申请实施例提供的方案进行了介绍。可以理解的是,PM任务管理器、EMS为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例,本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对PM任务管理器、EMS进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集 成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。需要说明的是,本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下,如图7所示为本申请实施例提供的一种创建PM任务的装置70,用于实现上述方法中PM任务管理器的功能。该创建PM任务的装置70可以是NM中或xNFM中部署的PM任务管理器,或者也可以是部署于xNFM与EMS之间的PM任务管理器。其中,该创建PM任务的装置70可以为芯片***。本申请实施例中,芯片***可以由芯片构成,也可以包含芯片和其他分立器件。如图7所示,创建PM任务的装置70可以包括:获取单元7001、发送单元7002以及接收单元7003。获取单元7001用于执行图5或图6中的S501,发送单元7002用于执行图5或图6中的S502、S507、S511,接收单元7003用于执行图5或图6中的S506、S515、S517。其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
进一步的,如图7所示,创建PM任务的装置70还可以包括处理单元7004,用于执行图6中的S510、S516、S518、S520、S523。
在采用集成划分各个功能模块的情况下,如图8所示为本申请实施例提供的一种创建PM任务的装置80,用于实现上述方法中PM任务管理器的功能。该创建PM任务的装置80可以是NM中或xNFM中部署的PM任务管理器,或者也可以是部署于xNFM与EMS之间的PM任务管理器。其中,该创建PM任务的装置80可以为芯片***。本申请实施例中,芯片***可以由芯片构成,也可以包含芯片和其他分立器件。创建PM任务的装置80包括至少一个处理模块801及通信模块802。示例性地,处理模块801可以用于执行图5或图6中的过程S501、S510、S516、S518、S520、S523;处理模块801可以通过通信模块802用于执行图5或图6中的过程S502、S506、S507、S511、S515、S517。具体参见方法示例中的详细描述,此处不做赘述。
创建PM任务的装置80还可以包括至少一个存储模块803,用于存储程序指令和/或数据。存储模块803和处理模块801耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接,可以是电性,机械或其它的形式,用于装置、单元或模块之间的信息交互。处理模块801可能和存储模块802协同操作。处理模块801可能执行存储模块802中存储的程序指令。所述至少一个存储模块中的至少一个可以包括于处理模块中。
当处理模块801为处理器,通信模块802为收发器,存储模块803为存储器,本申请实施例图8所涉及的创建PM任务的装置80可以为图4所示的通信装置40。
如前述,本申请实施例提供的创建PM任务的装置70或创建PM任务的装置80可以用于实施上述本申请各实施例实现的方法中PM任务管理器的功能,为了便于说明,仅示出了与本申请实施例相关的部分,具体技术细节未揭示的,请参照本申请各实施例。
在采用对应各个功能划分各个功能模块的情况下,如图9所示为本申请实施例提供的一种创建PM任务的装置90,用于实现上述方法中EMS的功能。该创建PM任务的装置90可以是EMS,也可以是EMS中的装置,也可以是能够和EMS匹配使用 的装置。其中,该创建PM任务的装置90可以为芯片***。本申请实施例中,芯片***可以由芯片构成,也可以包含芯片和其他分立器件。如图9所示,创建PM任务的装置90可以包括:接收单元9001、确定单元9002以及发送单元9003。其中,接收单元9001用于执行图5或图6中的S503、S508、S512、S521,确定单元9002用于执行图5或图6中的S504,发送单元9003用于执行图5或图6中的S505、S514。其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
进一步的,如图9所示,创建PM任务的装置90还可以包括处理单元9004,用于执行图6中的S509、S513、S519、S523。
在采用集成划分各个功能模块的情况下,如图10所示为本申请实施例提供的一种创建PM任务的装置100,用于实现上述方法中EMS的功能。该创建PM任务的装置100可以是EMS,也可以是EMS中的装置,也可以是能够和EMS匹配使用的装置。其中,该创建PM任务的装置100可以为芯片***。本申请实施例中,芯片***可以由芯片构成,也可以包含芯片和其他分立器件。创建PM任务的装置100包括至少一个处理模块1001及通信模块1002。示例性地,处理模块1001可以用于执行图5或图6中的过程S504、S509、S513、S519、S523;处理模块1001可以通过通信模块1002用于执行图5或图6中的过程S503、S505、S508、S512、S514、S521。具体参见方法示例中的详细描述,此处不做赘述。
创建PM任务的装置100还可以包括至少一个存储模块1003,用于存储程序指令和/或数据。存储模块1003和处理模块1001耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接,可以是电性,机械或其它的形式,用于装置、单元或模块之间的信息交互。处理模块1001可能和存储模块1002协同操作。处理模块1001可能执行存储模块1002中存储的程序指令。所述至少一个存储模块中的至少一个可以包括于处理模块中。
当处理模块1001为处理器,通信模块1002为收发器,存储模块1003为存储器,本申请实施例图10所涉及的创建PM任务的装置100可以为图4所示的通信装置40。
如前述,本申请实施例提供的创建PM任务的装置90或创建PM任务的装置100可以用于实施上述本申请各实施例实现的方法中EMS的功能,为了便于说明,仅示出了与本申请实施例相关的部分,具体技术细节未揭示的,请参照本申请各实施例。
本申请另一些实施例还提供一种计算机可读存储介质,该计算机可读存储介质可包括计算机软件指令,当该计算机软件指令在PM任务管理器上运行时,使得该PM任务管理器执行上述图5或图6所示实施例中PM任务管理器执行的各个步骤。
本申请另一些实施例还提供一种计算机可读存储介质,该计算机可读存储介质可包括计算机软件指令,当该计算机软件指令在EMS上运行时,使得该EMS执行上述图5或图6所示实施例中EMS执行的各个步骤。
本申请另一些实施例还提供一种计算机程序产品,当该计算机程序产品在计算机上运行时,使得该计算机执行上述图5或图6所示实施例中PM任务管理器或者EMS执行的各个步骤。
本申请另一些实施例还提供一种芯片***,该芯片***可以应用于PM任务管理 器或者EMS。该芯片***包括接口电路和处理器;接口电路和处理器通过线路互联;接口电路用于从终端的存储器接收信号,并向处理器发送信号,信号包括存储器中存储的计算机指令;当处理器执行该计算机指令时,芯片***执行如上述图5或图6所示实施例中PM任务管理器或者EMS执行的各个步骤。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现,也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成,软件模块可以被存放于RAM、闪存、ROM、可擦除可编程只读存储器(erasable programmable ROM,EPROM)、电可擦可编程只读存储器(electrically EPROM,EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器,从而使处理器能够从该存储介质读取信息,且可向该存储介质写入信息。当然,存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外,该ASIC可以位于核心网接口设备中。当然,处理器和存储介质也可以作为分立组件存在于核心网接口设备中。或者,存储器可以与处理器耦合,例如存储器可以是独立存在,通过总线与处理器相连接。存储器也可以和处理器集成在一起。存储器可以用于存储执行本申请实施例提供的技术方案的应用程序代码,并由处理器来控制执行。处理器用于执行存储器中存储的应用程序代码,从而实现本申请实施例提供的技术方案。
通过以上的实施方式的描述,所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,仅以上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将装置的内部结构划分成不同的功能模块,以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中,应该理解到,所揭露的装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述模块或单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个装置,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是一个物理单元或多个物理单元,即可以位于一个地方,或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个可读取存储介质中。基于这样的理解,本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该软件产品存储在一个存储介质中,包括若干指令用以使得一个设备(可以是单片机,芯片等)或处理器(processor)执行本申请各个实施例所述方法的 全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何在本申请揭露的技术范围内的变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。
Claims (21)
- 一种创建性能管理PM任务的方法,其特征在于,所述方法包括:PM任务管理器获取第一信息及混合网络服务NS的标识ID,所述第一信息包括所述NS中的物理网络功能PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息、上报周期的信息;所述第一信息用于指示创建按照所述收集周期搜集所述PNF的所述一个或多个性能指标,并按照所述上报周期信息上报搜集的性能指标的PM任务;所述PM任务管理器向网元管理***EMS发送所述第一信息;所述PM任务管理器从所述EMS接收第一PM任务的标识ID,所述第一PM任务是按照所述收集周期搜集所述PNF的所述一个或多个性能指标,并按照所述上报周期信息上报搜集的性能指标的PM任务;所述PM任务管理器向所述EMS发送所述第一PM任务的ID、所述混合NS的ID及订阅标识,所述订阅标识用于针对所述混合NS订阅所述第一PM任务。
- 根据权利要求1所述的方法,其特征在于,所述方法还包括:所述PM任务管理器将所述混合NS的ID与所述第一PM任务的ID对应记录,并标记所述第一PM任务的状态为订阅。
- 根据权利要求1或2所述的方法,其特征在于,所述PM任务管理器获取第一信息及NS的标识ID,包括:所述PM任务管理器从网络管理器NM接收所述第一信息及所述NS的ID;或者,所述PM任务管理器从网络功能虚拟化编排器NFVO接收所述第一信息及所述NS的ID;或者,所述PM任务管理器从网络功能管理器xNFM接收所述第一信息及所述NS的ID。
- 根据权利要求1-3任一项所述的方法,其特征在于,所述方法还包括:所述PM任务管理器接收第三PM任务的ID、所述混合NS的ID及删除标识,所述删除标识用于指示删除针对所述混合NS的所述第三PM任务;若不存在所述混合NS之外的其他网元使用所述第三PM任务,所述PM任务管理器通过所述EMS删除所述第三PM任务,并删除记录的所述第三PM任务与所述混合NS的ID的对应关系;若所述第三PM任务为订阅,且存在所述混合NS之外的其他网元使用所述第三PM任务,所述PM任务管理器取消订阅所述第三PM任务,并删除记录的所述第三PM任务与所述混合NS的ID的对应关系;若所述第三PM任务为新建,且存在所述混合NS之外的其他网元使用所述第三PM任务,删除记录的所述第三PM任务与所述混合NS的ID的对应关系。
- 一种混创建性能管理PM任务的方法,其特征在于,所述方法包括:网元管理***EMS从PM任务管理器接收第一信息,所述第一信息包括物理网络功能PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息、上报周期的信息;所述EMS确定存在第一PM任务,所述第一PM任务是按照所述收集周期搜集所述PNF的所述一个或多个性能指标,并按照所述上报周期信息上报搜集的性能指标的PM任务;所述EMS向所述PM任务管理器发送所述第一PM任务的标识ID;所述EMS从所述PM任务管理器接收所述第一PM任务的ID、混合网络服务NS的ID以及订阅标识,所述订阅标识用于针对所述混合NS订阅所述第一PM任务。
- 根据权利要求5所述的方法,其特征在于,所述方法还包括:所述EMS在执行所述第一PM任务后,按照所述上报周期信息,向所述PM任务管理器上报针对所述NS搜集的所述第一PM任务的性能指标;或者,所述EMS在执行所述第一PM任务后,按照所述上报周期信息,向网络管理器NM上报针对所述NS搜集的所述第一PM任务的性能指标。
- 根据权利要求5或6所述的方法,其特征在于,所述方法还包括:所述EMS从所述PM任务管理器接收第三PM任务的ID、所述混合NS的ID及取消订阅标识,所述取消订阅标识用于针对所述混合NS取消订阅所述第三PM任务;所述EMS在执行所述第三PM任务后,停止上报针对所述混合NS搜集的所述第三PM任务的性能指标。
- 根据权利要求5-7任一项所述的方法,其特征在于,所述方法还包括:所述EMS从所述PM任务管理器接收第三PM任务的ID及删除标识;所述EMS删除所述第三PM任务。
- 一种创建性能管理PM任务的装置,其特征在于,所述装置包括:获取单元,用于获取第一信息及网络服务NS的标识ID,所述第一信息包括所述NS中的物理网络功能PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息、上报周期的信息;所述第一信息用于指示创建按照所述收集周期搜集所述PNF的所述一个或多个性能指标,并按照所述上报周期信息上报搜集的性能指标的PM任务;发送单元,用于向网元管理***EMS发送所述第一信息;接收单元,用于从所述EMS接收所述第一PM任务的标识ID,所述第一PM任务是按照所述收集周期搜集所述PNF的所述一个或多个性能指标,并按照所述上报周期信息上报搜集的性能指标的PM任务;所述发送单元还用于向所述EMS发送所述第一PM任务的ID、所述混合NS的ID及订阅标识,所述订阅标识用于针对所述混合NS订阅所述第一PM任务。
- 根据权利要求9所述的装置,其特征在于,所述装置还包括:记录单元,用于将所述混合NS的ID与所述第一PM任务的ID对应记录,并标记所述第一PM任务的状态为订阅。
- 根据权利要求9或10所述的装置,其特征在于,所述获取单元具体用于:从网络管理器NM接收所述第一信息及所述NS的ID;或者,从网络功能虚拟化编排器NFVO接收所述第一信息及所述NS的ID;或者,从网络功能管理器xNFM接收所述第一信息及所述NS的ID。
- 根据权利要求9-11任一项所述的装置,其特征在于,所述接收单元还用于,接收第三PM任务的ID、所述混合NS的ID及删除标识,所述删除标识用于指示删除针对所述混合NS的所述第三PM任务;所述装置还包括处理单元,用于:若不存在所述混合NS之外的其他网元使用所述第三PM任务,通过所述EMS删除所述第三PM任务,并删除记录的所述第三PM任务与所述混合NS的ID的对应关系;若所述第三PM任务为订阅,且存在所述混合NS之外的其他网元使用所述第三PM任务,取消订阅所述第三PM任务,并删除记录的所述第三PM任务与所述混合NS的ID的对应关系;若所述第三PM任务为新建,且存在所述混合NS之外的其他网元使用所述第三PM任务,删除记录的所述第三PM任务与所述混合NS的ID的对应关系。
- 一种创建性能管理PM任务的装置,其特征在于,所述装置包括:接收单元,用于从PM任务管理器接收第一信息,所述第一信息包括物理网络功能PNF的标识信息、一个或多个性能指标的标识信息、收集周期的信息、上报周期的信息;确定单元,用于确定存在第一PM任务,所述第一PM任务是按照所述收集周期搜集所述PNF的所述一个或多个性能指标,并按照所述上报周期信息上报搜集的性能指标的PM任务;发送单元,用于向所述PM任务管理器发送所述第一PM任务的标识ID;所述接收单元还用于,从所述PM任务管理器接收所述第一PM任务的ID、混合网络服务NS的ID以及订阅标识,所述订阅标识用于针对所述混合NS订阅所述第一PM任务。
- 根据权利要求13所述的装置,其特征在于,所述装置还包括处理单元,用于:所述EMS在执行所述第一PM任务后,按照所述上报周期信息,向所述PM任务管理器上报针对所述NS搜集的所述第一PM任务的性能指标;或者,所述EMS在执行所述第一PM任务后,按照所述上报周期信息,向网络管理器NM上报针对所述NS搜集的所述第一PM任务的性能指标。
- 根据权利要求13或14所述的装置,其特征在于,所述接收单元还用于:从所述PM任务管理器接收接收第三PM任务的ID、所述混合NS的ID及取消订阅标识,所述取消订阅标识用于针对所述混合NS取消订阅所述第三PM任务;所述装置还包括处理单元,用于根据所述取消订阅标识的指示,在执行所述第三PM任务后,停止上报针对所述混合NS搜集的所述第三PM任务的性能指标。
- 根据权利要求13-15任一项所述的装置,其特征在于,所述接收单元还用于:从所述PM任务管理器接收第三PM任务的ID及删除标识;所述装置还包括处理单元,用于根据所述删除标识的指示,删除所述第三PM任务。
- 一种性能管理PM任务管理器,其特征在于,所述PM任务管理器包括:处理器,存储器;所述处理器和所述存储器耦合,所述存储器用于存储计算机程序代码,所述计算机程序代码包括计算机指令,当所述计算机指令被所述PM任务管理器执行时,使得所述PM任务管理器执行如权利要求1至4中任一项所述的创建PM任务的方法。
- 一种网元管理***EMS,其特征在于,所述EMS包括:处理器,存储器;所述处理器和所述存储器耦合,所述存储器用于存储计算机程序代码,所述计算机程序代码包括计算机指令,当所述计算机指令被所述EMS执行时,使得所述EMS执行如权利要求5至8中任一项所述的创建PM任务的方法。
- 一种计算机可读存储介质,其特征在于,包括:计算机软件指令;当所述计算机软件指令在性能管理PM任务管理器中运行时,使得所述PM任务管理器执行如权利要求1至4中任一项所述的创建PM任务的方法。
- 一种计算机可读存储介质,其特征在于,包括:计算机软件指令;当所述计算机软件指令在网元管理***EMS中运行时,使得所述EMS执行如权利要求5至8中任一项所述的创建PM任务的方法。
- 一种计算机程序产品,其特征在于,当所述计算机程序产品在计算机上运行时,使得所述计算机执行如权利要求1至8中任一项所述的创建PM任务的方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910928046.2A CN112583613B (zh) | 2019-09-27 | 2019-09-27 | 一种创建pm任务的方法及装置 |
CN201910928046.2 | 2019-09-27 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021057844A1 true WO2021057844A1 (zh) | 2021-04-01 |
Family
ID=75110371
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/117409 WO2021057844A1 (zh) | 2019-09-27 | 2020-09-24 | 一种创建pm任务的方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN112583613B (zh) |
WO (1) | WO2021057844A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105376083A (zh) * | 2014-08-25 | 2016-03-02 | 华为技术有限公司 | 节能控制方法、管理服务器和网络设备 |
WO2017164931A1 (en) * | 2016-03-23 | 2017-09-28 | Intel IP Corporation | Method and system to perform performance measurements job operations |
CN107431647A (zh) * | 2014-08-27 | 2017-12-01 | 适应性频谱和信号校正股份有限公司 | 用于实现接入节点功能的虚拟化的***、方法和装置 |
WO2017222609A1 (en) * | 2016-06-20 | 2017-12-28 | Intel IP Corporation | End-to-end techniques to collect pm (performance measurement) data from a nvf (network function virtualization) infrastructure |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8745234B2 (en) * | 2010-12-23 | 2014-06-03 | Industrial Technology Research Institute | Method and manager physical machine for virtual machine consolidation |
CN106209409B (zh) * | 2015-05-07 | 2019-04-12 | ***通信集团公司 | 一种基于虚拟网络功能vnf的调度消息处理方法及装置 |
WO2017196389A1 (en) * | 2016-05-11 | 2017-11-16 | Intel IP Corporation | Apparatus of performance measurement data subscription for nfv performance management |
CN109787803B (zh) * | 2017-11-15 | 2021-10-26 | 华为技术有限公司 | 管理共享网络功能的方法及装置 |
-
2019
- 2019-09-27 CN CN201910928046.2A patent/CN112583613B/zh active Active
-
2020
- 2020-09-24 WO PCT/CN2020/117409 patent/WO2021057844A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105376083A (zh) * | 2014-08-25 | 2016-03-02 | 华为技术有限公司 | 节能控制方法、管理服务器和网络设备 |
CN107431647A (zh) * | 2014-08-27 | 2017-12-01 | 适应性频谱和信号校正股份有限公司 | 用于实现接入节点功能的虚拟化的***、方法和装置 |
WO2017164931A1 (en) * | 2016-03-23 | 2017-09-28 | Intel IP Corporation | Method and system to perform performance measurements job operations |
WO2017222609A1 (en) * | 2016-06-20 | 2017-12-28 | Intel IP Corporation | End-to-end techniques to collect pm (performance measurement) data from a nvf (network function virtualization) infrastructure |
Also Published As
Publication number | Publication date |
---|---|
CN112583613A (zh) | 2021-03-30 |
CN112583613B (zh) | 2022-05-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3512233B1 (en) | Method for managing network slice and management unit | |
US10924966B2 (en) | Management method, management unit, and system | |
WO2019062994A1 (zh) | 网络切片的管理方法、设备及*** | |
WO2020052605A1 (zh) | 一种网络切片的选择方法及装置 | |
US20160164963A1 (en) | Method, system, and device for managing server hardware resources in a cloud scheduling environment | |
WO2019047911A1 (zh) | 一种物联网资源订阅的方法、设备和*** | |
US11088924B2 (en) | Network management method, device, and system | |
EP3531749B1 (en) | Management method, management unit and system for network function | |
WO2011130940A1 (zh) | 多业务统一处理方法及统一业务平台 | |
WO2021185083A1 (zh) | Vnf实例化方法及装置 | |
WO2021057378A1 (zh) | Vnf实例化方法、nfvo、vim、vnfm及*** | |
WO2020124930A1 (zh) | 一种资源的调度、处理方法及装置 | |
CN109417501A (zh) | 网络资源的编排方法和设备 | |
CN111586140A (zh) | 一种数据交互的方法及服务器 | |
KR101956320B1 (ko) | 트랜잭셔널 미들웨어 머신 환경에서 단일 포인트 병목을 방지하는 시스템 및 방법 | |
WO2021057844A1 (zh) | 一种创建pm任务的方法及装置 | |
WO2012167657A1 (zh) | 一种实现事件转发的方法及通用信息模型cim服务器 | |
CN107534678B (zh) | 建立vnfm与vim之间的连接的方法、装置及*** | |
WO2021022947A1 (zh) | 一种部署虚拟机的方法及相关装置 | |
CN107005468B (zh) | 一种待上载的nsd的确定方法及装置 | |
CN108632070B (zh) | 虚拟网络设备的配置方法及服务器 | |
CN114510325A (zh) | 任务调度方法、装置及*** | |
CN113098705B (zh) | 网络业务的生命周期管理的授权方法及装置 | |
US20230388844A1 (en) | Translating commands for legacy radio access network | |
WO2024016801A1 (zh) | 基站算力编排方法、装置、电子设备及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20867915 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20867915 Country of ref document: EP Kind code of ref document: A1 |