TW201735719A - Network function virtualization (NFV) performance measurement (PM) threshold monitoring operations - Google Patents

Abstract

Techniques for performing threshold monitoring operations (e.g., creation, deletion, or listing of one or more thresholds) in connection with virtual network function (VNF) related virtualization resource (VR) performance measurements (PMs) are discussed. A Network Manager (NM) can send a request to an Element Manager (EM) to perform a threshold monitoring operation, and the EM can send a request to a VNF manager (VNFM) to perform the threshold monitoring operation, which can send a request to a Virtualization Infrastructure Manager (VIM) to perform the threshold monitoring operation. The VIM can perform the threshold monitoring operation, and can send a reply to the VNFM indicating a result of the threshold monitoring operation, which can send a reply to the EM indicating the result of the threshold monitoring operation, which can send a reply to the NM indicating the result of the threshold monitoring operation.

Description

Network Function Virtualization (NFV) Effective Energy Measurement (PM) Threshold Monitoring Operation Technology

FIELD OF THE INVENTION The present disclosure relates to core network technologies for communication networks, and more particularly to operational techniques associated with thresholds for linking virtual network functions (VNFs).

BACKGROUND OF THE INVENTION Network Function Virtualization (NFV) involves replacing physical network nodes with virtual network functions (VNFs) implemented by virtualized resources (VRs) that perform the same functions as physical nodes.

In accordance with an embodiment of the present invention, a device that is configured to be employed within a network manager (NM) includes: a memory; and one or more processors are configured to: Making a decision, wherein the decision is to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM) for deleting a first existing Threshold to monitor a decision of the VNF-related VR PM, or to obtain a detail of one or more existing thresholds to monitor a decision of the VNF-related VR PM; send a request to an element manager (EM), where The request of the EM is: in response to the decision generating the new threshold for the decision to generate to monitor a request of the VNF-related VR PM to the EM, in response to the decision being the decision to delete Deleting the existing threshold to monitor one of the VNF-related VR PM requests to the EM, or in response to the decision to list the threshold identified by a list of threshold identifiers to obtain the decision Requesting; and receiving a response from the EM, wherein from the EM The response is: in response to the request to the EM being a response to the request for the EM indicating a threshold to generate a result from the EM, in response to the request to the EM being deleted Responding to one of the EMs for the request of the EM to indicate a result of one of the threshold deletions, or in response to the request to the EM indicating the one or more of the request to the EM for the list The details of an existing threshold are responded to by one of the EMs.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT The present disclosure is now described with reference to the drawings, in which like reference numerals As used herein, the terms "component", "system", "interface" and the like are intended to refer to computer-related entities, hardware, software (eg, in execution), and/or firmware. For example, a component can be a processor (eg, a microprocessor, controller, or other processing device), a processor running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and/or user equipment with processing devices (eg, mobile phones, etc.). By way of illustration, the application and server running on the server can also be components. One or more components can reside within a processing program, and a component can be limited to a single computer and/or can be distributed between two or more computers. A collection of elements or a collection of other components can be described herein, wherein the term "set" can be interpreted as "one or more."

Moreover, such components can be executed from a variety of computer readable storage media having various data structures stored thereon, such as using modules. The components may be processed by local and/or remote processing, such as by having one or more data packets (eg, data from a component and in a local system, a decentralized system, and/or across a network, such as the Internet) Signal communication over a network, regional network, wide area network, or another component of a similar network with a system that interacts through signals.

As another example, a component can be one having a particular function provided by a mechanical component that is operated by electrical or electronic circuitry, wherein the electrical or electronic circuitry can be a software application or firmware that is executed by one or more processors. Application operation. The one or more processors can be internal or external to the device and can execute at least a portion of the software or firmware application. In yet another example, a component can be one of the specific functions provided by the electronic component without mechanical components; the electronic components can include one or more processors therein to perform, at least in part, the electronic components Functional software and / or firmware.

The use of the text paradigm is intended to present concepts in a concrete manner. As used in this case, the term "or" is intended to mean an inclusive "or" rather than a mutually exclusive "or". In other words, "X employs A or B" is intended to mean any of the natural inclusions unless otherwise stated or apparent from the context. In other words, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" in either case. In addition, the articles "a" and "an" are used in the context of the application and the scope of the accompanying claims, unless otherwise stated or indicated in the context. To indicate "one or more". In addition, the terms "including", "including", "having", "having", "having" or variations thereof are used in the detailed description and the scope of the patent application. These terms are intended to be similar terms. The way to include is inclusive.

As used herein, the term "circuitry" may mean, may be a component thereof, or may include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or grouped), and/or executed. Or multiple software or firmware programs (shared, dedicated, or grouped), combinatorial logic, and/or other suitable hardware components that provide the functionality. In some embodiments, the circuitry can be implemented, or the associated functionality of the circuitry can be implemented by one or more software or firmware modules. In some embodiments, the circuitry can include logic that is at least partially operable in a hardware.

The embodiments described herein can be implemented as a system using any suitably assembled hardware and/or software. Figure 1 illustrates components of a network in accordance with several embodiments. In various aspects, some or all of one or more of the components illustrated in connection with FIG. 1 can be implemented to interface with the various oriented virtual network functions (VNFs) described herein. The evolved packet core (EPC) network 100 is shown to include a home subscriber server (HSS) 110, an mobility management entity (MME) 120, a service gateway (SGW) 130, and a packet data network (PDN) gateway ( PGW) 140, Policy and Charging Rules Function (PCRF) 150

The HSS 110 includes one or more databases for network users, including subscription-related information to support the processing of network entities in the communication connection phase. For example, HSS 110 may provide support for routing/roaming, authentication, authorization, naming/address resolution, location dependencies, and the like. The EPC network 100 may include one or more HSSs 110 depending on the number of mobile users, the capacity of the equipment, the organizational structure of the network, and the like.

The MME 120 functions like the control plane of the legacy General Packet Radio Service (GPRS) Support Node (SGSN). The MME 120 manages the mobility of access to such things as gateway selection and tracking area list management. EPC network 100 may include one or several MMEs 120.

The SGW 130 ends the interface towards the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) and determines the path of the data packets between the E-UTRAN and the EPC network 100. In addition, SGW 130 may be a local mobility anchor for handover between evolved Node Bs, and may also provide anchoring for mobility between 3GPPs. Other responsibilities may include legal interception, billing, and several policy enforcements.

PGW 140 ends the SGi interface towards the PDN. The PGW PGW 140 arranges data packets between the EPC network 100 and the external network, and may be nodes for policy enforcement and billing data collection. PCRF 150 is the policy and charging control component of EPC network 100. In a non-roaming scenario, there may be a single PCRF in the Local Public Land Mobile Network (HPLMN) associated with the User Equipment (UE) Internet Protocol Connectivity Access Network (IP-CAN) connection phase. In a roaming scenario with a local data breach, there may be two PCRFs associated with the UE's IP-CAN connection phase: a local PCRF (H-PCRF) within the HPLMN and a visit to the local public land mobile network ( VPLMN) Internal Visit PCRF (V-PCRF). The PCRF 150 can be communicatively coupled to an application server (also known as an application function (AF)). In summary, the application server uses the Internet Protocol (IP) bearer resources with the core network for the components that provide the application (eg, UMTS Packet Service (PS) Definition Domain, Long Term Evolution (LTE) PS Data services, etc.). The application server can send PCRF 150 to indicate the new service flow and select the appropriate quality of service (QoS) and charging parameters. PCRF 150 may provide this rule as a Policy and Charging Enforcement Function (PCEF) (not shown) with appropriate Data Flow Template (TFT) and identifier QoS Class (QCI), as provided by the application server. Start QoS and billing.

The components of EPC 100 can be implemented in one physical node or in separate physical nodes. In some embodiments, Network Function Virtualization (NFV) is used to virtualize any of the previously described network node functions via executable instructions stored in one or more computer readable storage media. Or all (more details later). A logical specific illustration of the EPC network 100 may be referred to as a network cut slice 101. A logically specific illustration of a portion of the EPC network 100 may be referred to as a network sub-cut slice 102 (eg, the network sub-cut slice 102 is shown to include the PGW 140 and the PCRF 150).

2 is a block diagram illustrating that a component can read instructions from a machine readable or computer readable medium (machine readable storage medium) and perform any one or more of the methods discussed herein in accordance with several embodiments. By. More specifically, FIG. 2 shows a graphical representation of a hardware resource 200 that includes one or more processors (or processor cores) 210, one or more memory/storage devices 220, and one or A plurality of communication resources 230, each of which is communicatively coupled via bus bar 240. For embodiments utilizing node virtualization (e.g., NFV), hypervisor 202 can be executed to provide an execution environment for one or more network fragmentation/sub-cut slices to utilize hardware resources 200.

The processor 210 (eg, a central processing unit (CPU), a reduced instruction set computer (RISC) processor, a complex instruction set computer (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband A processor, an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), other processors, or any suitable combination thereof, for example, can include processor 212 and processor 214. The memory/storage device 220 can include a primary memory, a disk storage device, or any suitable combination thereof.

Communication resources 230 may include interconnect and/or network interface components or other suitable means for communicating with one or more peripheral devices 204 and/or one or more databases 206 via network 208. For example, communication resource 230 can include wired communication components (eg, for coupling through a universal serial bus (USB)), cellular communication components, near field communication (NFC) components, Bluetooth® components (eg, Bluetooth®) Low energy), Wi-Fi® components, and other communication components.

The instructions 250 can include software, programs, applications, applets, mobile applications, or other executable code to cause at least one of the processors 210 to perform any one or more of the methods discussed herein. By. The instructions 250 may reside entirely or partially within at least one of the processor 210 (eg, within the cache memory of the processor), the memory/storage device 220, or any suitable combination thereof. Again, any portion of the instructions 250 can be transferred from the peripheral device 204 and/or the database 206 to any of the hardware resources 200. Accordingly, the memory, memory/storage device 220, peripheral device 204, and database 206 of the processor 210 are examples of computer readable and machine readable media.

In various embodiments, the techniques described herein may be employed to generate, delete, and/or list linked VNF-related virtualized resource (VR) energy measurement (PM) related thresholds, and/or generate such threshold crossings. Notice.

To ensure that virtualized network functions (VNFs) deployed on the Network Function Virtualization (NFV) Infrastructure (NFVI) deliver consistent, acceptable quality of service to end users, and to isolate and correct faults in the most timed manner In the case, virtualized resource (VR) energy measurement (PM) can be employed. This equivalent energy measurement reflects how the VNF is affected by the NFVI service, and the unique nature of the service is provided by NFVI, such as CPU, virtual machine, memory, and virtual network. Therefore, NFV efficacy measurements can be measured in VNF and NFVI.

However, in order to identify possible problems with self-efficacy data, conventional operators first collect performance for several days, weeks, or even months, and then screen large amounts of data, which can be time consuming and costly due to the processing power involved. Even though these prior art techniques may eventually identify problems from PM data exploration, it may be too late to be mitigated because of the dynamic fluctuations in network traffic.

In various embodiments discussed herein, threshold monitoring operations, including threshold generation, threshold deletion, and threshold lists, can be employed to monitor VNF-related VR energy measurements. Threshold cross notifications can be reported when the cross threshold is measured.

Referring to FIG. 3, an outline of an architecture for assisting VR effect energy threshold monitoring and/or threshold crossing notification in accordance with various aspects described herein is illustrated. In FIG. 3, various described implementation-oriented virtualized network function (VNF) energy measurement (PM) threshold generation flows (and selectively consecutive threshold crossing notifications) can be coupled to the threshold cross notification flow along with the threshold crossing notification flow as a threshold Monitor the operation instance. The system illustrated in FIG. 3 includes a network manager (NM) 310, a network function virtualization (NFV) planner (NFVO) 320, a network element manager (EM) 330, and an NFV infrastructure (NFVI) 350. the virtual network virtualization function (VNF) resources (VR) of a virtual set of 370 _i, VNF manager (VNFM) 340, and virtual infrastructure Manager (VIM) 360. The solid lines between these entities indicate various reference points that aid in the exchange of data between such entities, the dashed lines indicate the data streams associated with the threshold generation, and the solid dashed lines indicate the data streams associated with the threshold crossing notifications.

Referring to FIG. 4, a schematic diagram showing a threshold generation process for monitoring a VR PM data program in accordance with various aspects described herein, showing monitoring of a VR effect measurement threshold and generating a notification when a threshold crossing or performance alarm is detected is illustrated. Process instance. In various aspects, the techniques described herein can be employed to perform threshold monitoring operations (eg, threshold generation, deletion, listing, etc.), and to notify NMs and/or operators of such thresholds that intersect. The flow of Figure 4 shows a contextual example involving the generation of thresholds and subsequent triggers.

In FIG. 4, the NM may send a request to the EN to generate one or more thresholds that may be delimited by parameters, such as iOCName (Information Target Class (IOC) name), iOCInstanceList (IOC case list), thresholdInfoList (threshold information list, It may indicate a threshold for a particular type of energy measurement (eg, by one or more measurement types), etc. to monitor VNF-related VR energy measurements.

At 2, the EM may send a request to the VNFM to generate a threshold for monitoring the type of measurement specified in the thresholdInfoList on the VNF case identified by the iOCName and the iOCInstanceList.

3, the VNFM may send a request to the VIM to generate a threshold for monitoring the virtualized resource identified by the resource selector parameter (in the face-to-face, the measurement type in the thresholdInfoList provided by the EM is mapped to the resource selector in multiple ways. Any one of them).

At 4, the VIM can send a response to the VNFM with a thresholdId parameter that identifies the threshold that has been generated.

At 5, the VNFM can send a response to the EM with the generated threshold identifier.

At 6, the EM may send a response to the NM with the monitorId parameter, which may indicate a unique identifier of the thresholdMonitor (eg, the threshold at which the PM is or may be monitored by the link), which may have a status field Has a Success value.

At 7, the VIM may send a ThresholdCrossedNotification to the VNFM, which may have a threshold ID (eg, through the thresholdId parameter) indicating a threshold that has crossed.

At 8, the VNFM may send a notification to the EM indicating a threshold that has been cross-identified by the threshold ID. The VNFM can send a VR performance alert notification to the EM.

At 9, the EM can send a VNF-related VR performance alert notification to the NM.

In various aspects, the techniques discussed herein can be employed in conjunction with threshold monitoring operations, such as threshold generation, threshold deletion, and threshold lists. The following use cases provide contextual instances involving the generation, deletion, and listing of thresholds, and associated actions that may be performed by NM, EM, VNFM, and/or VIM linking such threshold monitoring operations.

Table 1 below shows examples of use cases for threshold generation to monitor one or more VNF-related VR energy measurements: Table 1: Threshold generation for monitoring VNF-related VR energy measurements

Table 2 below shows examples of use cases for monitoring threshold deletions for monitoring one or more VNF-related VR energy measurements: Table 2: Threshold deletions for monitoring VNF-related VR energy measurements

Table 3 below shows an example of a use case for a list of thresholds for monitoring one or more VNF-related VR energy measurements: Table 3: Threshold list for monitoring VNF-related VR energy measurements

Moreover, in various aspects, the techniques discussed herein can be linked to various thresholds to produce threshold crossing notifications. Table 4 below shows examples of use cases for VR energy threshold crossing notifications: Table 4: VR Energy Energy Threshold Cross Notification

Moreover, in various aspects, the functionality of one or more of the reference points in FIG. 3 can be modified to support the threshold monitoring and notification operations discussed herein. For example, in various embodiments, the Ve-Vnfm-em reference point can have the following capabilities: (a) The Ve-Vnfm-em reference point can support the ability to allow the EM to request VNFM to generate thresholds to monitor VNF-related VR performance. (b) The Ve-Vnfm-em reference point supports the ability to allow the VNFM to notify the EM threshold of the result; (c) the Ve-Vnfm-em reference point supports the ability to allow the EM to request VNFM deletion. To monitor the threshold of the VNF-related VR energy measurement; (d) The Ve-Vnfm-em reference point can support the following capabilities, allowing the VNFM to notify the result of the EM threshold deletion; (e) the Ve-Vnfm-em reference point can support the following Capabilities that allow the EM to request the VNFM list to use to monitor one, multiple, or all thresholds of the VNF-related VR energy measurement; (f) the Ve-Vnfm-em reference point can support the ability to allow the VNFM to notify the EM threshold list of results (g) The Ve-Vnfm-em reference point can support the ability to allow the VNFM to notify the EM when a threshold crossing of the VNF-related VR energy measurement is detected. In the face-to-face, other reference points involving threshold monitoring and notification operations may similarly have the ability to support the operations described herein.

Referring to FIG. 5, a block diagram of a system 500 for assisting threshold monitoring and/or notification operations for VNF-related VR PMs in accordance with various aspects described herein is illustrated. Depending on the embodiment, system 500 can be coupled to one or more of NM, EM, VNFM, or VIM. System 500 can include one or more processors 510 (eg, which can include one or more of processors 210, etc.), communication circuitry 520 (which can communicate via one or more reference points, networks, etc.) And may include communication resources 230, etc., and memory 530 (which may include any of a variety of storage media, and may be stored in association with at least one of one or more processors 510 or communication circuits 520) Instructions and/or materials, and may include memory/storage device 220 and/or cache memory of processor 510, etc.). In some aspects, one or more processors 510, communication circuits 520, and memory 530 can be included in a single device, while in other aspects, they can be included in different devices, such as components of a decentralized architecture. . As will be described in detail later, depending on the embodiment, system 500 can facilitate threshold monitoring and/or notification operations for any of NM, EM, VNFM, and/or VIM.

Embodiments of the first set of systems 500 are related to NM-associated embodiments. In one embodiment of system 500 associated with NM, processor 510 can determine to implement a threshold monitoring operation (eg, based on operator input, etc.). The determined threshold monitoring operation may be to generate a threshold to monitor the VNF-related VR PM, delete the threshold to monitor the VNF-related VR PM, or determine details about one or more threshold monitoring VNF-related VR PMs.

In an aspect involving the generation of a threshold in the NM, the processor 510 can send a request to the EM to generate a new threshold, and can receive a response from the NM indicating the result of the request to the EM to generate a new threshold. In a detailed example, the request sent by the processor 510 can indicate one or more destination networks (DNs) of one or more measurement types of ManagedEntity cases that are to be monitored by the generated thresholds, which are permeable. IOC case list (iOCInstanceList) parameter indication. In this aspect, the request sent by processor 510 may also include one or more IOC Name (iOCName) parameters that specify a managed entity class name for each of the ManagedEntity cases specified by the iOCInstanceList parameter. And may include one or more threshold information list (thresholdInfoList) parameters that specify a particular measurement type for the new threshold to be generated. The response received by the processor 510 from the EM may indicate the status of the request to the EM, eg, success, failure, or partial success, and may also indicate, such as indicating the identity of the generated threshold through the associated monitorId parameter.

In the aspect involving the NM deletion threshold, the processor 510 can send a request to the EM to delete the current threshold, and can receive a response from the NM indicating the result of the EM request to delete the current threshold. In a detailed example, the request for the EM may indicate the threshold to be aborted and removed via the associated identifier (eg, the monitorId parameter may indicate the unique identifier of the thresholdMonitor, which may indicate that the VNF-related VR PM is monitored Or may be monitored for associated thresholds, etc., and responses from the NM may indicate a request status for the EM, such as success or failure.

In the aspect involving the NM list threshold, the processor 510 can send a request to the EM to list one or more thresholds, and can receive a response from the NM indicating its result to the EM request list for one or more thresholds. In a detailed example, the request for the EM may include a parameter (eg, monitorIdList parameter) indicating a threshold to be listed, and a response from the EM may indicate the status of the request (eg, success or failure), and may indicate a match The threshold of the standard stated in the request for EM. In some aspects, the request can contain a list of blank thresholds, and the response can include a list of all thresholds.

Moreover, in an NM embodiment of system 500, processor 510 can receive (eg, from EM, through an Itf-N reference point) one or more current thresholds for monitoring VNF-related VR PMs (eg, by threshold generation operations) A threshold generated) that may indicate that the associated threshold has crossed.

Referring to Figure 6, a flow diagram of a method 600 of assisting a threshold monitoring operation by NM in accordance with various aspects described herein is illustrated. In some aspects, method 600 can be performed at NM. In other aspects, the machine readable medium may store an associated indication of method 600 that, when executed, may cause NM to perform the acts of method 600.

At 610, the linked VNF-related VR PM can select a threshold monitoring operation, such as generation of one or more thresholds, deletion of one or more thresholds, or a list of one or more thresholds.

At 620, the request can be sent to the EM for a selected threshold monitoring operation (eg, generate, delete, list, etc.).

At 630, a response can be received from the EM indicating the result of the selected threshold monitoring operation.

At 640, a threshold crossing notification can be received indicating that the current threshold (eg, a threshold generated by 610-630, or a previously generated threshold, etc.) has crossed.

Referring again to FIG. 5, an embodiment of the second set of systems 500 relates to an EM-associated embodiment. In an embodiment of system 500 associated with EM, processor 510 can receive a first request from NM to perform the indicated threshold monitoring operation (eg, generate a threshold to monitor VNF-related VR PM, delete monitoring VNF-related VR PM The threshold, or list, monitors one or more thresholds of the VNF-related VR PM).

Involving the aspect of the threshold generation of the EM, the processor 510 can receive the first request from the NM to generate a new threshold to monitor the VNF-related VR PM, and can send a second request to the VNFM to generate a new threshold. Processor 510 can receive a first response from VNFM indicating a second request to generate a new threshold, and can send a second response to NM, the response can indicate a first request to produce a new threshold result. In the detailed example, the first request from the NM and the second response to the NM may include the parameters described above in connection with the NM embodiment of the system 500. Additionally, the second request to the VNFM can include a source selector parameter that can specify one or more measurement types associated with the new threshold and can be identified and updated by one or more additional parameters Additional details associated with the threshold, such as a performanceMetric parameter, a threshold type parameter, and/or a threshold detail parameter. The first response from the VNFM may include a threshold value (thresholdId) parameter that identifies the threshold generated.

In the aspect involving threshold deletion in the EM, the processor 510 can receive the first request from the NM to delete the threshold for monitoring the VNF-related VR PM, and can send a second request to the VNFM to delete the threshold. The processor 510 can receive a result of the first response from the VNFM indicating the second request to delete the threshold, and can send a result to the NM second response that can indicate the first request to delete the threshold. In the medium-facing, the first request from the NM and the second response to the NM may include the parameters described above in connection with the NM embodiment of the system 500.

In the aspect involving the threshold list of the EM, the processor 510 can receive the first request from the NM to monitor one or more thresholds of the VNF-related VR PM, and can send the second request to the VNFM to list the threshold. The processor 510 can receive a first response from the VNFM indicating the second request to list the result of the one or more thresholds, and can send to the NM a second response that can indicate the first request to list the one or more thresholds. In the medium-facing, the first request from the NM and the second response to the NM may include the parameters described above in connection with the NM embodiment of the system 500.

Moreover, in an NM embodiment of system 500, processor 510 can receive (eg, from VNFM, through the Ve-Vnfm-em reference point) a notification that the thresholds on the VNF-related VR PM have crossed. In response, the processor 510 can add a VNF-related VR performance alert associated with the crossed threshold to the alert list and can send a VNF-related VR performance alert notification to the NM.

Referring to Figure 7, a flow diagram of a method 700 of assisting a threshold monitoring operation by an EM in accordance with various aspects described herein is illustrated. In some aspects, method 700 can be performed at EM. In other aspects, the machine readable media may store an associated indication of the method 700 that, when executed, may cause the EM to perform the actions of the method 700.

At 710, a request can be received from the NM to perform a specified threshold monitoring operation (eg, threshold generation, threshold deletion, threshold list, etc.) that joins the VNF-related VR PM.

At 720, a request can be sent to the VNFM for a specified threshold monitoring operation.

At 730, a response may be received from the VNFM indicating the result of the specified threshold monitoring operation (eg, success, failure, list of thresholds, etc.).

At 740, a response can be sent to the NM indicating the result of the specified threshold monitoring operation.

Optionally, at 750, a notification threshold can be received from the VNFM (eg, as indicated by the thresholdId parameter) that has been crossed.

At 760, in response to 750 receiving the notification, by adding a VNF-related VR performance alert to the alert list based on the crossed threshold, a performance alert can be determined to be generated.

At 770, a VNF-related VR performance alert notification can be sent to the NM based on the 760-plus VNF-related VR performance alert added to the alert list.

Referring again to FIG. 5, an embodiment of the third set of systems 500 is associated with an embodiment of VNFM. The processor 510 can receive a request from the EM to perform a threshold monitoring operation, which can involve threshold generation, threshold deletion, or a threshold list.

In the aspect of threshold generation involving VNFM, processor 510 can receive a first request from the EM to generate a new threshold to monitor the VNF-related VR PM, and can send a second request to generate a new threshold to the VIM. The processor 510 can receive a first response from the VIM indicating the result of the second request to generate the new threshold, and can send the result of the first request to the EM second response indicating the generation of the new threshold.

In the aspect of the threshold deletion involving VNFM, the processor 510 can receive a first request to delete a threshold for monitoring the VNF-related VR PM from the EM, and a second request that can be sent to the VIM deletion threshold. The processor 510 can receive a first response from the VIM as a result of the second request indicating the deletion threshold, and can send the result of the first request to the EM second response indicating the deletion threshold.

In the aspect of the VNFM threshold list, the processor 510 can receive a first request for monitoring one or more thresholds of the VNF-related VR PM from the EM, and a second request that can be sent to the VNFM list for one or more thresholds. The processor 510 can receive the result of the second request of the first response indication list one or more thresholds from the VNFM, and can send the result of the first request to the NM second response indication list one or more thresholds. In the medium-facing, the first request from the NM and the second response to the NM may include parameters as described in the NM embodiment of the foregoing connection system 500.

Further, processor 510 can detect that the VNF-related VR PM has crossed the current threshold, which can be based on a threshold crossing notification received from the VIM. In the face-to-face, the threshold crossing notification from the VIM may include one or more parameters indicating relevant details of the threshold crossing and/or threshold crossing. Based on the processor 510 detecting that the threshold has crossed, the processor 510 can send a threshold crossing notification to the EM, the notification can include one or more parameters indicating relevant details of the threshold crossing and/or threshold crossing, such as objectInstanceId parameter, thresholdId Parameters, crossingDirection parameters, performanceMetric parameters, and/or performanceValue parameters.

Referring to Figure 8, a flow diagram of a method 800 of assisting threshold monitoring operations by VNFM in accordance with various aspects described herein is illustrated. In some aspects, method 800 can be performed on VNFM. In other aspects, the machine readable medium can store an associated indication of the method 800 that, when executed, can cause the VNFM to perform the actions of the method 800.

At 810, a request can be received from the EM to perform a specified threshold monitoring operation (eg, threshold generation, threshold deletion, threshold list, etc.) that joins the VNF-related VR PM.

At 820, a request can be sent to the VIM for a specified threshold monitoring operation.

At 830, a response may be received from the VIM indicating the result of the specified threshold monitoring operation (eg, success, failure, list of thresholds, etc.).

At 840, a response can be sent to the EM indicating the result of the specified threshold monitoring operation.

Optionally, at 850, a notification threshold can be received from the VNFM (eg, as indicated by the thresholdId parameter) that has been crossed.

At 860, a threshold crossing notification can be sent to the EM based on the notification thresholds received from the VIM having crossed.

Referring again to FIG. 5, a fourth set of embodiments of system 500 pertains to VIM-associated embodiments. Processor 510 can receive a request from a EM to perform a threshold monitoring operation, which can involve threshold generation, threshold deletion, or a threshold list.

In the aspect involving threshold generation in the VIM, the processor 510 can receive a request to generate a new threshold from the VNFM, can generate a new threshold, and can send a response to the VNFM indicating the result of the threshold generation (eg, a threshold identifier, etc.).

In the aspect involving threshold deletion in the VIM, the processor 510 may receive a request to delete the threshold from the VNFM, may delete the threshold, and may send a response to the VNFM indicating the result of the threshold deletion.

In the aspect of the threshold list involved in the VIM, the processor 510 may receive a list of one or more threshold requests from the VNFM, may generate a list of one or more thresholds, and may send a response to the VNFM indication list one or more thresholds The result of the request (for example, a list of thresholds, etc.).

In addition, processor 510 can detect threshold crossings associated with existing thresholds and send a threshold crossing notification to VNFM based on the detected threshold crossings, which can identify thresholds that have been crossed and can provide additional information regarding threshold crossings. In some aspects, processor 510 can detect threshold crossings based on monitoring existing VNF-related VR PM links. In other aspects, processor 510 detects threshold crossings based on notifications of threshold crossings received from NFVI.

Referring to Figure 9, a flow diagram of a method 900 of assisting a threshold monitoring operation by a VIM in accordance with various aspects described herein is illustrated. In some aspects, method 900 can be performed at VIM. In other aspects, the machine readable medium may store an associated indication of the method 900 that, when executed, may cause the VIM to perform the actions of the method 900.

At 910, a request can be received from the VNFM for a specified threshold monitoring operation (eg, generating, deleting, or listing one or more thresholds for a VNF-related VR PM, etc.).

At 920, a specified threshold monitoring operation can be performed.

At 930, a response can be sent to the VNFM indicating the result of the specified threshold monitoring operation.

At 940, optionally, a threshold (eg, generated at 920 or previously existing) linked to the VNF-related VR PM may detect a threshold crossing. The threshold crossing can be detected by receiving a notification from the NFVI or by monitoring the VNF related VR PM for the threshold.

At 950, based on the threshold crossing detected by 940, the threshold crossing notification can be sent to the VNFM which can identify the threshold that has been crossed and additional information associated with the threshold crossing.

The examples herein may include a subject matter, such as a method, means for performing an action, or a block of methods, at least one machine readable medium comprising executable instructions that are borrowed from a machine (eg, a processor with memory, a particular application integrated circuit) The (ASIC), Field Programmable Gate Array (FPGA), etc., when executed, cause the machine to perform the actions of the method or the operation of the device or system in accordance with the described embodiments and examples using a plurality of communication technologies for simultaneous communication.

Example 1 is a device that is configured to be employed within a network manager (NM), comprising: a memory; and one or more processors configured to: make a decision, wherein the decision A decision to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM) for generating a new threshold for deleting a first existing threshold to monitor the VNF related VR PM a decision to monitor the VNF-related VR PM with details of one or more existing thresholds; send a request to an element manager (EM), wherein the request to the EM is: response The decision to generate the new threshold for generating the new threshold to monitor the request of the VNF-related VR PM to the EM, in response to the decision to delete the existing threshold for the decision to delete to monitor the VNF Requesting one of the VR PMs to the EM, or in response to the decision to list the threshold identified by a list of threshold identifiers for the decision to obtain one of the requests to the EM; and receiving a request from the EM In response, the response from the EM is: responding to the EM Retrieving a response from the EM indicating a result of a threshold generation for generating the request to the EM, in response to the request to the EM being a request to delete the request to the EM One of the results of the threshold deletion is responsive to one of the EMs, or the request to the EM is the request to the EM to indicate the details of the one or more existing thresholds from the EM A response.

Example 2 includes the subject matter of any variation of any of the examples 1, wherein the one or more processors are further configured to receive a VNF-related VR performance alert notification from the EM.

Example 3 includes the subject matter of any variation of any of the examples 1-2, wherein the request to the EM is the request to generate the EM.

Example 4 includes the subject matter of any variation of any of the examples 3, wherein the request to the EM includes an information target category (IOC) case list (iOCInstanceList) parameter indicating one or more of its measurementTypes to be monitored One or more destination networks (DNs) of the ManagedEntity case.

Example 5 includes the subject matter of any variation of any of the examples 4, wherein the request to the EM includes an IOC name (iOCName) parameter for the one or more ManagedEntity cases specified by the iOCInstanceList parameter Each contains a ManagedEntity category name.

Example 6 includes the subject matter of any variation of any of the examples 3, wherein the request to the EM includes a threshold information list (thresholdInfoList) parameter indicating the new threshold for one or more particular measurementTypes.

Example 7 includes the subject matter of any variation of any of the examples 1-2, wherein the request to the EM is the request to the EM for deletion, and the request to the EM includes the A monitor identity (monitorId) parameter of a ThresholdMonitor that is stopped and removed.

Example 8 includes the subject matter of any variation of any of the examples 1-2, wherein the request to the EM is the request to the EM for the list, and the request to the EM includes the A monitor identity list (monitorIdList) parameter for the list of ThresholdMonitors.

Example 9 is a device that is configured to be employed within an element manager (EM), comprising: a memory; and one or more processors configured to: from a network manager (NM) Receiving a first request, wherein the first request from the NM is: generating a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM) from the a first request by the NM to delete an existing threshold to monitor a first request from the NM of the VNF-related VR PM, or to list a threshold identified by a list of threshold identifiers from the NM a first request; sending a second request to a VNF manager (VNFM), wherein the second request to the VNFM is: responding to the first request from the NM as being generated from the NM The first request is used to generate the new threshold to monitor a second request of the VNF-related VR PM to the VNFM, in response to the first request from the NM being the first request from the NM for deletion To remove the existing threshold to monitor the second request of the VNF-related VR PM to the VNFM, or to respond to the first request from the NM Determining, for the list, the first request from the NM to list the second request to the VNFM of the thresholds identified by the threshold identifier of the list; receiving a first response from the VNFM, wherein The first response from the VNFM includes: responding to the second request to the VNFM that one or more identifiers of the one or more thresholds for the second request to be generated for the VNFM are generated, the response The second request to the VNFM is one or more identifiers for deleting the one or more thresholds of the second request to the VNFM, or the second request to the VNFM is The second request to the VNFM for the list includes details of one or more thresholds; and sends a second response to the NM, wherein the second response to the NM indicates that the response is from the VNFM The first response includes the one or more identifiers of the one or more thresholds being generated to indicate a result of the first request to generate the new threshold, in response to the first response from the VNFM The one or more identifiers of the one or more thresholds are deleted to indicate In addition to the first one to request the result of the existing thresholds, or in response to the first response from the VNFM to include such details of one or more threshold values and indicates those details of such a threshold value or more.

Example 10 includes the subject matter of any variation of any of the examples 9, wherein the one or more processors are further configured to: receive a notification from the VNF manager (VNFM) to the VNF-related VR PM The previous threshold has been crossed; a VNF-related VR performance alert is added to an alert list to determine a performance alert; and a VNF-related VR performance alert notification is sent to the NM.

Example 11 includes the subject matter of any of the variations of any of the examples 9-10, wherein the first request from the NM is for the first request from the NM and the second request to the VNFM is for use The second request to the VNFM is generated.

Example 12 includes the subject matter of any variation of any of the examples 11, wherein the second request to the VNFM includes a source selector parameter specifying one or more measurement types.

Example 13 includes the subject matter of any variation of any of the examples 11, wherein the second request to the VNFM includes a PerformanceMetric parameter, a ThresholdType parameter, and a thresholdDetails parameter generated for monitoring in the sourceSelector parameter The new threshold of the one or more measurement types of the explicit.

Example 14 includes the subject matter of any variation of any of the examples 11, wherein the first response from the VNFM includes a threshold identity parameter indicating one of the new thresholds that have been generated.

Example 15 includes the subject matter of any variation of any of the examples 11, wherein the second response to the NM includes a monitor identity (monitorId) indicating a unique identifier of a ThresholdMonitor associated with the new threshold The parameter, and a state parameter that contains one of the values of "Success".

Example 16 includes the subject matter of any of the variations of any of the examples 9-10, wherein the first request from the NM is for the first request from the NM and the second request to the VNFM is for use The second request to delete the VNFM, and the second response to the NM, includes a state parameter having a value of "Success", "Failure", or "PartialSuccess".

Example 17 includes the subject matter of any of the variations of any of the examples 9-10, wherein the first request from the NM is for the first request from the NM for the list and the second request to the VNFM is for The second request to the VNFM in the list, and the second response to the NM include a monitor information list (monitorInfoList) parameter containing the echo information corresponding to the ThresholdMonitors matching input criteria.

Example 18 includes the subject matter of any of the variations of any of the examples 11-12, wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a thresholdDetails parameter generated for monitoring the sourceSelector parameter The new threshold of the one or more measurement types set forth in the description.

Example 19 includes the subject matter of any variation of any of examples 11-12 or 18, wherein the first response from the VNFM includes a threshold identity parameter indicating an identifier of the new threshold that has been generated .

Example 20 is a device that is configured to be employed within a Virtual Network Function (VNF) Manager (VNFM), comprising: a memory; and one or more processors configured to: The component manager (EM) receives a request, wherein the request from the EM is to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM). Request from one of the EMs to delete an existing threshold to monitor one of the VNF-related VR PM requests from the EM, or to list a threshold identified by a list of threshold identifiers from one of the EMs And sending a response to the EM, wherein the response to the EM indicates that one or more of the plurality of thresholds are indicated in response to the request from the EM for the request for the EM to be generated Generating, in response to the request from the EM indicating that one or more identifiers of the plurality of thresholds are deleted for the request for the deletion from the EM, or in response to the request from the EM being used The details of the list are indicated by the request from the EM.

Example 21 includes the subject matter of any variation of any of the examples 20, wherein the one or more processors are further configured to detect that the VNF-related VR PM has crossed a first threshold.

Example 22 includes the subject matter of any variation of any of the examples 21, wherein the one or more processors are further configured to send a notification to the EM that the first threshold has been crossed on the VNF-related VR PM .

Example 23 includes the subject matter of any variation of any of the examples 22, wherein the notification includes a target instance identity (objectInstanceId) parameter identifying the first threshold.

The example 24 includes the subject matter of any variation of any of the examples 22, wherein the notification includes a thresholdId parameter, a crossingDirection parameter, a performanceMetric parameter, and a performanceValue parameter indicating that the first threshold has crossed.

Example 25 includes the subject matter of any variation of any of the examples 21, wherein the one or more processors are further configured to be based on a threshold crossing notification received from a Virtualized Infrastructure Manager (VIM) It is detected that the VR PM has crossed the first threshold.

Example 26 includes the subject matter of any of the variations of any of the examples 20-25, wherein the one or more processors are further configured to: send an additional request to a virtualized infrastructure manager (VIM), The additional request indication to the VIM in response to the request from the EM indicating the request from the EM for the request to be generated from the EM, in response to the request from the EM being Deleting the request from the EM for deletion of the request from the EM, or in response to the request from the EM being the request for the list from the request for the EM The request for the EM; and receiving an additional response from the Virtual Infrastructure Manager (VIM), wherein the additional request to the VIM indicates the additional request from the VIM to generate the request from the EM Responding to a result of the request for the EM to be generated, in response to the additional request to the VIM indicating the request for deletion from the EM indicating the request for deletion from the EM, Or responding to the additional request indication to the VIM to generate the self The request for the EM indicates the request from the EM for the request.

Example 27 includes the subject matter of any of the examples 20-25, wherein the request from the EM is the request to generate from the EM, and wherein the response to the EM includes an indication that the indication has been generated A threshold identity (thresholdId) parameter of one of the new thresholds.

Example 28 is a device that is configured to be employed within a virtualized infrastructure manager (VIM), comprising: a memory; and one or more processors configured to: process from a virtualized network One of the Road Function (VNF) Manager (VNFM) requests, wherein the request from the VNFM is associated with a Virtual Network Function (VNF) related Virtualization Resource (VR) Effectiveness Measurement (PM) threshold monitoring The request from the VNFM is one of an existing threshold for monitoring a VNF-related VR PM from the VNFM to generate a new threshold for deleting one of its existing thresholds for monitoring the VNF-related VR PM Request from one of the VNFMs of the existing threshold, or one of the existing thresholds of the set of existing thresholds indicated by a list of threshold identifiers, from one of the VNFMs; responsive to the VNFM The request, one of: responding to the request from the VNFM to generate the new threshold for the request from the VNFM to monitor the VNF-related VR PM, in response to the request from the VNFM Delete the set for the request to delete from the VNFM The indicated existing threshold in the existing threshold, or in response to the request from the VNFM being one of the existing thresholds for monitoring the second set of VNF-related VR PMs for the request from the VNFM for the list And transmitting a response to the VNFM in response to generating the new threshold indicating the result of the request for the VNFM to be generated, in response to deleting the indicated threshold indicating the request for deletion from the VNFM The result, or in response to generating the list, indicates the result of the request from the VNFM for the list.

Example 29 includes the subject matter of any variation of any of the examples 28, wherein the one or more processors are further configured to transmit a threshold associated with one of an existing threshold of the set that has crossed an existing threshold A cross notification is sent to the VNFM, wherein the threshold cross notification indicates an associated identifier for one of the already existing thresholds.

Example 30 includes the subject matter of any variation of any of the examples 29, wherein the one or more processor systems are further configured to detect a threshold crossing associated with the crossed existing threshold, and wherein the one Or a plurality of processors are configured to generate the threshold crossing notification in response to the threshold crossing.

Example 31 includes the subject matter of any variation of any of the examples 29, wherein the one or more processors are further configured to receive an additional threshold crossing notification from a Network Function Virtualization Infrastructure (NFVI), And the one or more processors are configured to generate the threshold crossing notification in response to the additional threshold crossing notification received from the NFVI.

Example 32 is a machine readable medium containing instructions that, when executed, cause a network manager (NM) to: make a decision, wherein the decision is to generate a new threshold to monitor a virtual A decision of a Virtual Network Function (VNF) related Virtualization Resource (VR) Energy Measurement (PM) to delete a first existing threshold to monitor a decision of the VNF-related VR PM, or to obtain one or more A decision of the existing threshold to monitor a decision of the VNF-related VR PM; sending a request to an element manager (EM), wherein the request to the EM is: in response to the decision being the decision to generate Generating the new threshold to monitor a request from the VNF-related VR PM to the EM, in response to the decision deleting the existing threshold for the decision to delete to monitor a request for the VNF-related VR PM to the EM, Or responding to the request to list one of the EMs for which the threshold identified by the threshold identifier of the list is used to obtain the decision; and receive a response from the EM, wherein the response from the EM is: Responding to the request to the EM for the generation to the E The request of M indicates that a threshold value is generated from one of the EM responses, and the request to the EM is a result of indicating a threshold deletion for the request to the EM for deletion. One of the EMs responds, or responds to the request to the EM as one of the EM responses to the list of instructions for the EM indicating the details of the one or more existing thresholds.

Example 33 includes the subject matter of any variation of any of the examples 32, wherein the instructions, when executed, further cause the NM to receive a VNF-related VR performance alert notification from the EM.

The example 34 includes the subject matter of any variation of any of the examples 32-33, wherein the request to the EM is the request to generate the EM.

Example 35 includes the subject matter of any variation of any of the examples 34, wherein the request to the EM includes an information target category (IOC) case list (iOCInstanceList) parameter indicating one or more of its measurementTypes to be monitored One or more destination networks (DNs) of the ManagedEntity case.

Example 36 includes the subject matter of any of the variations of any of the examples 35, wherein the request to the EM includes an IOC name (iOCName) parameter for the one or more ManagedEntity cases specified by the iOCInstanceList parameter Each contains a ManagedEntity category name.

The example 37 includes the subject matter of any variation of any of the examples 34, wherein the request to the EM includes a thresholdInfoList parameter indicating the new threshold for one or more particular measurementTypes.

Example 38 includes the subject matter of any of the examples 32-33, wherein the request to the EM is the request to delete the EM, and wherein the request to the EM includes A monitor identity (monitorId) parameter of a ThresholdMonitor that is stopped and removed.

Example 39 includes the subject matter of any of the examples 32-33, wherein the request to the EM is the request to the EM for listing, and wherein the request to the EM includes A monitor identity list (monitorIdList) parameter for the list of ThresholdMonitors.

Example 40 is a machine readable medium containing instructions that, when executed, cause an element manager (EM) to: receive a first request from a network manager (NM), wherein from the NM The first request is: a first threshold from the NM for generating a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM), to delete one An existing threshold to monitor a first request from the NM of the VNF-related VR PM, or a first request from the NM to list a threshold identified by a list of threshold identifiers; send a second request to a VNF Manager (VNFM), wherein the second request to the VNFM is: in response to the first request from the NM being the first request from the NM to generate the new threshold for monitoring The second request of the VNF-related VR PM to the VNFM, in response to the first request from the NM being the first request from the NM to delete the existing threshold to monitor the VNF-related VR a second request from the PM to the VNFM, or in response to the first request from the NM as a list from the NM The first request is for listing a second request to the VNFM of the thresholds identified by the threshold identifier of the list; receiving a first response from the VNFM, wherein the first response from the VNFM comprises Responding to the second request to the VNFM that one or more identifiers of the one or more thresholds for the second request to be generated for the VNFM are generated in response to the second request to the VNFM Deleting one or more identifiers of the one or more thresholds for the second request to the VNFM to be deleted, or responding to the second request to the VNFM as the list to the VNFM The second request includes details of one or more thresholds; and sends a second response to the NM, wherein the second response to the NM indicates that the first response from the VNFM includes the one or more The one or more identifiers of the thresholds are generated to indicate a result of the first request to generate the new threshold, in response to the first response from the VNFM including the one or more thresholds Waiting for one or more identifiers to be deleted to indicate the first to delete the existing threshold One result of the request, or in response to the first response from the VNFM to include such details of one or more threshold values and indicates those details of such a threshold value or more.

Example 41 includes the subject matter of any variation of any of the examples 40, wherein the instructions, when executed, further cause the EM to: receive a notification from the VNF manager (VNFM) to the VNF-related VR PM A threshold has been crossed; a VNF-related VR performance alert is added to an alert list to determine a performance alert; and a VNF-related VR performance alert notification is sent to the NM.

Example 42 includes the subject matter of any of the variations of any one of the examples 40-41, wherein the first request from the NM is for the first request from the NM and the second request to the VNFM is for use The second request to the VNFM is generated.

Example 43 includes the subject matter of any variation of any of the examples 42 wherein the second request to the VNFM includes a sourceSelector parameter specifying one or more measurement types.

The example 44 includes the subject matter of any variation of any of the examples 42 wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a thresholdDetails parameter, the generation of the parameter for monitoring the sourceSelector parameter The new threshold of the one or more measurement types of the explicit.

The example 45 includes the subject matter of any variation of any of the examples 42 wherein the first response from the VNFM includes a threshold identity parameter indicating an identifier of the new threshold that has been generated.

Example 46 includes the subject matter of any variation of any of the examples 42 wherein the second response to the NM includes a monitor identity (monitorId) indicating a unique identifier of a ThresholdMonitor associated with the new threshold The parameter, and a state parameter that contains one of the values of "Success".

The example 47 includes the subject matter of any of the examples 40-41, wherein the first request from the NM is for the first request from the NM and the second request to the VNFM is for use The second request to delete the VNFM, and the second response to the NM, includes a state parameter having a value of "Success", "Failure", or "PartialSuccess".

Example 48 includes the subject matter of any of the examples 40-41, wherein the first request from the NM is for the first request from the NM for the list and the second request to the VNFM is for The second request to the VNFM in the list, and the second response to the NM include a monitor information list (monitorInfoList) parameter containing the echo information corresponding to the ThresholdMonitors matching input criteria.

Example 49 includes the subject matter of any of the examples 42-43, wherein the second request to the VNFM includes a PerformanceMetric parameter, a ThresholdType parameter, and a thresholdDetails parameter generated for monitoring the sourceSelector parameter The new threshold of the one or more measurement types set forth in the description.

The example 50 includes the subject matter of any variation of any one of the examples 42-43 or 49, wherein the first response from the VNFM includes a threshold identity (thresholdId) parameter indicating one of the new thresholds that has been generated. .

Example 51 is a machine readable medium containing instructions that, when executed, cause a Virtual Network Function (VNF) Manager (VNFM) to: receive a request from an Element Manager (EM), wherein The request from the EM is to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM) request from the EM to delete one An existing threshold to monitor a request from the EM of the VNF-related VR PM, or to request a list of thresholds identified by a list of threshold identifiers from the EM; and send a response to the EM, wherein The response indication of the EM is responsive to the request from the EM indicating that one or more identifiers of the plurality of thresholds are generated for the request from the EM to be generated, in response to the request from the EM Indicating that one or more identifiers of the plurality of thresholds are deleted for the request to delete from the EM, or in response to the request from the EM being the request for the list from the EM The details of the threshold.

The example 52 includes the subject matter of any variation of any of the examples 51, wherein the instructions, when executed, further cause the VNFM to detect that the VNF-related VR PM has crossed a first threshold.

The example 53 includes the subject matter of any variation of any of the examples 52, wherein the instructions, when executed, further cause the VNFM to send a notification to the EM that the first threshold has crossed on the VNF-related VR PM.

The example 54 includes the subject matter of any variation of any of the examples 53 wherein the notification includes a target instance identity (objectInstanceId) parameter identifying the first threshold.

The instance 55 includes the subject matter of any variation of any of the examples 53 wherein the notification includes a thresholdId parameter, a crossingDirection parameter, a performanceMetric parameter, and a performanceValue parameter indicating that the first threshold has crossed.

Example 56 includes the subject matter of any of the variations of any of the examples 52, wherein the instructions, when executed, further cause the VNFM to detect the threshold based on a threshold crossing notification received from a Virtualized Infrastructure Manager (VIM) The VR PM has crossed the first threshold.

Instance 57 includes the subject matter of any of the examples 51-56, wherein the instructions, when executed, further cause the VNFM to: send an additional request to a Virtualized Infrastructure Manager (VIM), The additional request indication to the VIM in response to the request from the EM indicating the request from the EM for the request to be generated from the EM, in response to the request from the EM being Deleting the request from the EM for deletion of the request from the EM, or in response to the request from the EM being the request for the list from the request for the EM The request for the EM; and receiving an additional response from the Virtual Infrastructure Manager (VIM), wherein the additional request to the VIM indicates the additional request from the VIM to generate the request from the EM Responding to a result of the request for the EM to be generated, in response to the additional request to the VIM indicating the request for deletion from the EM indicating the request for deletion from the EM, Or responding to the additional request indication to the VIM for production The request from the EM's and indicating that the request for the list from the EM.

Example 58 includes the subject matter of any of the examples 51-56, wherein the request from the EM is the request to generate from the EM, and wherein the response to the EM includes an indication that the indication has been generated A threshold identity (thresholdId) parameter of one of the new thresholds.

Example 59 is a machine readable medium containing instructions that, when executed, cause a virtualized infrastructure manager (VIM) to: process from a virtualized network function (VNF) manager (VNFM) a request, wherein the request from the VNFM is associated with a thresholding monitoring of a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM), wherein the request from the VNFM is for Generating a new threshold to monitor a request from the VNFM of the VNF-related VR PM to delete one of the VNFM requests for monitoring an existing threshold of one of an existing threshold of a set of VNF-related VR PMs, Or requesting one of the existing thresholds of the set indicated by a list of threshold identifiers from one of the VNFMs; in response to the request from the VNFM, one of: The request from the VNFM generates the new threshold for the request generated from the VNFM to monitor the VNF-related VR PM, and the request from the VNFM is the request for the deletion from the VNFM. And deleting the existing threshold of the collection An existing threshold, or a list of existing thresholds for monitoring the second set of VNF-related VR PMs for the request from the VNFM in response to the request from the VNFM; and sending a response to The VNFM is responsive to the result of generating the new threshold indicating the request for the request from the VNFM, in response to deleting the indicated threshold indicating the result of the request for deletion from the VNFM, or in response to generating The list indicates the result of the request from the VNFM to be used for the list.

The example 60 includes the subject matter of any of the variations of any of the examples 59, wherein the instructions, when executed, further cause the VIM to send a threshold cross notification associated with one of the existing thresholds of the set having crossed an existing threshold To the VNFM, wherein the threshold crossing notification indicates an associated identifier for one of the already crossed existing thresholds.

Example 61 includes the subject matter of any variation of any of the examples 60, wherein the instructions, when executed, further cause the VIM to detect a threshold crossing associated with the crossed existing threshold, and wherein the one or more The processors are configured to generate the threshold crossing notification in response to the threshold crossing.

The example 62 includes the subject matter of any variation of any of the examples 60, wherein the instructions, when executed, further cause the VIM to receive an additional threshold cross notification from a network function virtualization infrastructure (NFVI), and The one or more processors are configured to generate the threshold crossing notification in response to the additional threshold crossing notification received from the NFVI.

Example 63 is a device that is configured to be employed within a network manager (NM), comprising: means for storing instructions; and means for processing are configured to execute the instructions to: A decision, wherein the decision is to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM) to delete a first existing threshold a decision to monitor the VNF-related VR PM, or to obtain a detail of one or more existing thresholds to monitor a decision of the VNF-related VR PM; send a request to an element manager (EM), to the The request of the EM is: in response to the decision generating the new threshold for the decision to generate to monitor the request of the VNF-related VR PM to the EM, in response to the decision being deleted for the decision to delete The existing threshold to monitor one of the VNF-related VR PM requests to the EM, or in response to the decision to list the threshold identified by a list of threshold identifiers to obtain the decision to obtain one of the EM requests And receiving a response from the EM, wherein the The response is: in response to the request to the EM being a response to the request for the EM indicating a threshold to generate a result from the EM, in response to the request to the EM being deleted Responding to one of the EMs for the request of the EM to indicate a result of one of the threshold deletions, or in response to the request to the EM indicating the one or more of the request to the EM for the list The details of an existing threshold are responded to by one of the EMs.

The example 64 includes the subject matter of any variation of any of the examples 63, wherein the means for processing is further configured to execute the instructions to receive a VNF-related VR performance alert notification from the EM.

Example 65 includes the subject matter of any variation of any of examples 63-64, wherein the request to the EM is the request to generate the EM.

The example 66 includes the subject matter of any variation of any of the examples 65, wherein the request to the EM includes an information target category (IOC) case list (iOCInstanceList) parameter indicating one or more of its measurementTypes to be monitored One or more destination networks (DNs) of the ManagedEntity case.

Example 67 includes the subject matter of any variation of any of the examples 66, wherein the request to the EM includes an IOC name (iOCName) parameter for the one or more ManagedEntity cases specified by the iOCInstanceList parameter Each contains a ManagedEntity category name.

The example 68 includes the subject matter of any variation of any of the examples 65, wherein the request to the EM includes a thresholdInfoList parameter that specifies the new threshold for one or more particular measurementTypes.

Example 69 includes the subject matter of any of the examples 63-64, wherein the request to the EM is the request to the EM for deletion, and the request to the EM includes the request to be A monitor identity (monitorId) parameter of a ThresholdMonitor that is stopped and removed.

The example 70 includes the subject matter of any of the examples 63-64, wherein the request to the EM is the request to the EM for the list, and the request to the EM includes the A monitor identity list (monitorIdList) parameter for the list of ThresholdMonitors.

Example 71 is an apparatus assembled to be employed within an element manager (EM), comprising: means for storing instructions; and means for processing to assemble the instructions to execute the instructions: The network manager (NM) receives a first request, wherein the first request from the NM is to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy Detecting (PM) a first request from the NM to delete an existing threshold to monitor a first request from the NM of the VNF-related VR PM, or to identify that the list is identified by a list of threshold identifiers a first request from the NM; sending a second request to a VNF Manager (VNFM), wherein the second request to the VNFM is: responding to the first request from the NM The first request generated from the NM is used to generate the new threshold to monitor a second request of the VNF-related VR PM to the VNFM, in response to the first request from the NM being deleted The first request of the NM is used to delete the existing threshold to monitor the second request of the VNF-related VR PM to the VNFM Or responding to the first request from the NM as a first request from the NM for listing the second request to the VNFM for listing the thresholds identified by the threshold identifier of the list; Receiving a first response from the VNFM, wherein the first response from the VNFM includes: responding to the second request to the VNFM as one of one or more thresholds for the second request to the VNFM to be generated Or a plurality of identifiers are generated, and the second request to the VNFM is one or more identifiers of the second request to the VNFM for deletion, or one or more identifiers are deleted, or the response is The second request to the VNFM includes details of one or more thresholds for the second request to the VNFM; and sends a second response to the NM, wherein the second to the NM Response indication: in response to the first response from the VNFM, the one or more identifiers including the one or more thresholds being generated to indicate a result of the first request to generate the new threshold, the response The first response from the VNFM includes one or more of the one or more thresholds The identifier is deleted to indicate a result of one of the first requests to delete the existing threshold, or to indicate the one or more in response to the first response from the VNFM including the one or more thresholds These details of the threshold.

The example 72 includes the subject matter of any variation of any of the examples 71, wherein the means for processing is further configured to execute the instructions to: receive a notification from the VNF manager (VNFM) to the VNF The previous VR PM threshold has been crossed; a VNF-related VR performance alert is added to an alert list to determine a performance alert; and a VNF-related VR performance alert notification is sent to the NM.

The example 73 includes the subject matter of any of the examples 71-72, wherein the first request from the NM is for the first request from the NM and the second request to the VNFM is for use The second request to the VNFM is generated.

The example 74 includes the subject matter of any variation of any of the examples 73, wherein the second request to the VNFM includes a sourceSelector parameter that specifies one or more measurement types.

The example 75 includes the subject matter of any of the variations of any one of the examples 73, wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a thresholdDetails parameter, the generation of the parameter for monitoring the sourceSelector parameter The new threshold of the one or more measurement types of the explicit.

The example 76 includes the subject matter of any variation of any of the examples 73, wherein the first response from the VNFM includes a threshold identity parameter indicating an identifier of the new threshold that has been generated.

Example 77 includes the subject matter of any variation of any of the examples 73, wherein the second response to the NM includes a monitor identity (monitorId) indicating a unique identifier of a ThresholdMonitor associated with the new threshold The parameter, and a state parameter that contains one of the values of "Success".

The example 78 includes the subject matter of any of the examples 71-72, wherein the first request from the NM is for the first request from the NM and the second request to the VNFM is for use The second request to delete the VNFM, and the second response to the NM, includes a state parameter having a value of "Success", "Failure", or "PartialSuccess".

The example 79 includes the subject matter of any of the examples 71-72, wherein the first request from the NM is for the first request from the NM for the list and the second request to the VNFM is for The second request to the VNFM in the list, and the second response to the NM include a monitor information list (monitorInfoList) parameter containing the echo information corresponding to the ThresholdMonitors matching input criteria.

The example 80 includes the subject matter of any of the examples 73-74, wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a thresholdDetails parameter generated for monitoring the sourceSelector parameter The new threshold of the one or more measurement types set forth in the description.

The example 81 includes the subject matter of any variation of any one of the examples 73-74 or 80, wherein the first response from the VNFM includes a threshold identity parameter indicating an identifier of the new threshold that has been generated .

Example 82 is a device that is configured to be employed within a Virtual Network Function (VNF) Manager (VNFM), comprising: means for storing instructions; and means for processing are configured to execute The instructions receive a request from an element manager (EM), wherein the request from the EM is to generate a new threshold to monitor a virtualized network function (VNF) related virtualization resource (VR). A request from one of the EMs to remove an existing threshold to monitor a request from the EM for the VNF-related VR PM, or to list a threshold identified by a list of threshold identifiers Requesting from one of the EMs; and sending a response to the EM, wherein the response to the EM indicates that a plurality of thresholds are indicated in response to the request from the EM for the request for the EM to be generated One or more identifiers are generated, indicating that one or more identifiers of the plurality of thresholds are deleted in response to the request from the EM for the request to delete from the EM, or The request by the EM indicates the details of the plurality of thresholds for the request from the EM to list.

The example 83 includes the subject matter of any variation of any of the examples 82, wherein the means for processing is further configured to execute the instructions to detect that the VNF-related VR PM has crossed a first threshold.

The example 84 includes the subject matter of any of the variations of any one of the examples 83, wherein the means for processing is further configured to execute the instructions to send a notification to the EM that the first threshold is associated with the VNF Cross on VR PM.

The example 85 includes the subject matter of any variation of any of the examples 84, wherein the notification includes a target instance identity (objectInstanceId) parameter identifying the first threshold.

The instance 86 includes the subject matter of any variation of any of the examples 84, wherein the notification includes a thresholdId parameter, a crossingDirection parameter, a performanceMetric parameter, and a performanceValue parameter indicating that the first threshold has crossed.

The example 87 includes the subject matter of any variation of any of the examples 83, wherein the means for processing is further configured to execute the instructions for receiving based on a received from a virtualized infrastructure manager (VIM) The threshold crossing notification detects that the VR PM has crossed the first threshold.

The example 88 includes the subject matter of any of the examples 82-87, wherein the means for processing is further configured to execute the instructions to: send an additional request to a virtualized infrastructure manager (VIM), wherein the additional request indication to the VIM is responsive to the request from the EM for the request for the EM to be generated from the request for the EM, in response to the request from the EM The request is for the deletion of the request from the EM to indicate the request for deletion from the EM, or the request for the request from the EM is indicated by the request for the EM for the list Receiving an additional response from the EM in the list; and receiving an additional response from the virtual infrastructure manager (VIM), wherein the request to the EM is generated in response to the additional request to the VIM The additional response of the VIM indicating a result of the request for the EM to be generated, in response to the additional request to the VIM indicating the request for deletion from the EM indicating the deletion from the EM The request, or the additional request to the VIM The request from the EM is indicated for the request to be generated from the EM.

Example 89 includes the subject matter of any of the examples 82-87, wherein the request from the EM is the request to generate from the EM, and wherein the response to the EM includes an indication that the indication has been generated A threshold identity (thresholdId) parameter of one of the new thresholds.

Example 90 is a device that is configured to be employed within a virtualized infrastructure manager (VIM), comprising: means for storing instructions; and means for processing to assemble the instructions to execute the instructions Processing a request from one of the Virtual Network Function (VNF) Managers (VNFM), wherein the request from the VNFM is related to a Virtualized Network Function (VNF) related Virtualization Resource (VR) energy measurement ( The threshold monitoring of the PM) is associated with the request from the VNFM to generate a new threshold to monitor the request of the VNF-related VR PM from the VNFM for deleting a set of monitoring the VNF-related VR PM One of the existing thresholds is requested from one of the VNFMs, or one of the existing thresholds of the set of existing thresholds indicated by the threshold identifier of the list is indicated by one of the existing thresholds Responding to the request from the VNFM, one of: responding to the request from the VNFM to generate the new threshold for the request from the VNFM to monitor the VNF-related VR PM, responding The request from the VNFM is for the deletion The request of the VNFM deletes the indicated existing threshold in the existing threshold of the set, or generates a monitoring of the VNF-related VR PM in response to the request from the VNFM for the request from the VNFM for the list. a list of existing thresholds of the second set; and transmitting a response to the VNFM in response to generating the new threshold indicating the result of the request for the VNFM to be generated, in response to deleting the indicated threshold indication for The result of the request being deleted from the VNFM, or in response to generating the list indicating the result of the request from the VNFM for the list.

The example 91 includes the subject matter of any of the variations of any one of the examples 90, wherein the means for processing is further configured to execute the instructions to transmit an existing threshold value that has been crossed with one of the set of existing thresholds A threshold crossing notification is sent to the VNFM, wherein the threshold crossing notification indicates an associated identifier for one of the crossed existing thresholds.

The example 92 includes the subject matter of any of the variations of any of the examples 91, wherein the means for processing is further configured to execute the instructions to detect a threshold crossing associated with the crossed existing threshold, and The one or more processors are configured to generate the threshold crossing notification in response to the threshold crossing.

Example 93 includes the subject matter of any variation of any of the examples 91, wherein the means for processing is further configured to execute the instructions to receive an additional from a Network Function Virtualization Infrastructure (NFVI) A threshold crossing notification, and wherein the one or more processors are configured to generate the threshold crossing notification in response to the additional threshold crossing notification received from the NFVI.

Example 94 is a device configured to be employed within a network manager (NM), comprising: a memory; and one or more processors configured to: select a link to a virtualized network function (VNF) a threshold monitoring operation of a Virtualization Resource (VR) Effective Energy Measurement (PM), wherein the selected threshold monitoring operation is generated as one of a new threshold, one of an existing threshold is deleted, or one or more One of a list of existing thresholds; sending a request to an element manager (EM) for performing the selected threshold monitoring operation; and receiving a response from the EM indicating a result of the selected threshold monitoring operation .

The example 95 includes the subject matter of any variation of any of the examples 94, wherein the one or more processors are further configured to receive a VNF-related VR performance alert from the EM.

Example 96 is a device that is configured to be employed within an element manager (EM), comprising: a memory; and one or more processors configured to: from a network manager (NM) Receiving a first request for performing a specified threshold monitoring operation for linking a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM), wherein the specified threshold monitoring operation is one of a new threshold Generating, deleting one of the existing thresholds, or one of one or more of the existing thresholds; transmitting a second request to a VNF Manager (VNFM) to perform the specified threshold monitoring operation; receiving one from the VNFM The first response is indicative of one of the results of the specified threshold monitoring operation; and a second response is sent to the NM indicating a result of the specified threshold monitoring operation.

The example 97 includes the subject matter of any of the variations of any one of the examples 96, wherein the one or more processors are further configured to: receive a notification from a VNF manager (VNFM) that a threshold has been applied to the VNF Corresponding VR PM crossover; by adding a VNF-related VR performance alert to an alert list, determining to generate a performance alert; and sending a VNF-related VR performance alert notification to the NM.

Example 98 is an apparatus configured to be employed within an element manager (EM), comprising: a memory; and one or more processors configured to: receive from an element manager (EM) a first request for performing a specified threshold monitoring operation for concatenating a VNF-related virtualized resource (VR) energy measurement (PM), wherein the specified threshold monitoring operation is generated as one of a new threshold, and one of the existing thresholds is deleted Or one of one or more of the existing threshold lists; transmitting a second request to a Virtualized Infrastructure Manager (VIM) to perform the specified threshold monitoring operation; receiving a first response from the VIM The specified threshold monitors one of the results of the operation; and sends a second response to the EM which indicates one of the results of the specified threshold monitoring operation.

The example 99 includes the subject matter of any variation of any of the examples 98, wherein the one or more processors are further configured to detect that the VNF-related VR PM has crossed a first threshold.

The instance 100 is a device that is configured to be employed within a virtualized infrastructure manager (VIM), including: a memory; and one or more processors configured to: from a virtualized network A function (VNF) manager (VNFM) receives a request for a specified threshold monitoring operation to link a VNF-related virtualized resource (VR) energy measurement (PM), wherein the specified threshold monitoring operation is generated as one of a new threshold And deleting one of the existing thresholds, or one of the one or more existing thresholds; performing the specified threshold monitoring operation; and transmitting a response to the VNFM indicating the result of the specified threshold monitoring operation.

Example 101 includes the subject matter of any variation of any of the examples 100, wherein the one or more processors are further configured to be sent to the VNFM associated with one of an existing threshold of the set that has crossed an existing threshold A threshold crossing notification, wherein the threshold crossing notification indicates an associated identifier for the crossed existing threshold.

The above description of the exemplary embodiments disclosed herein is intended to be illustrative, and is not intended to be While the specific embodiments and examples are described herein for illustrative purposes, it will be apparent to those skilled in the art that the various modifications are in the scope of the embodiments and examples.

In view of this, the subject matter of the present disclosure is to be construed as being limited to the various embodiments and the accompanying drawings. The same, similar, substituted, or substituted functions of the subject matter are disclosed without departing from the scope. Therefore, the subject matter disclosed herein is not limited to any single embodiment described herein, but is to be interpreted in terms of scope and scope in accordance with the appended claims.

In particular, the various functions performed by the components or structures (assembly, device, circuit, system, etc.) described above are used, unless otherwise indicated, the terms used to describe such components (including "components") are intended to correspond. Any component or structure that performs a particular function of the component (e.g., it is functionally equivalent), even if it is not structurally equivalent to the disclosed structure that functions in the specific embodiments illustrated herein. In addition, although only one of the several embodiments has disclosed a particular feature, such features may be combined with one or more other features of other embodiments as desired and preferred for any given or particular application.

100‧‧‧Evolved Packet Core (EPC) Network
101‧‧‧Network cutting piece
102‧‧‧Network sub-cutting piece
110‧‧‧Home User Server (HSS)
120‧‧‧Action Management Entity (MME)
130‧‧‧Service Gateway (SGW)
140‧‧‧ Packet Data Network (PDN) Gateway (PGW)
150‧‧‧Strategy and Billing Rules Function (PCRF)
200‧‧‧ hardware resources
202‧‧‧Super Manager
204‧‧‧ Peripheral devices
206‧‧‧Database
208‧‧‧Network
210, 212, 214, 510‧‧ ‧ processor, processor core
220, 530‧‧‧ memory/storage device
240‧‧‧ busbar
250‧‧‧ directive
310‧‧‧Network Manager (NM)
320‧‧‧Network Function Virtualization (NFV) Planner (NFVO)
330‧‧‧Network Element Manager (EM)
340‧‧‧VNF Manager (VNFM)
350‧‧‧NFV Infrastructure (NFVI)
360‧‧‧Virtual Infrastructure Manager (VIM)
370‧‧‧Virtual Networking Function (VNF)
500‧‧‧ system
520‧‧‧Communication circuit
600, 700, 800, 900 ‧ ‧ methods
610-640, 710-770, 810-860, 910-950‧‧‧ action blocks

1 is a block diagram illustrating components of a network in accordance with several embodiments.

2 is a block diagram illustrating that a component can read instructions from a machine readable or computer readable medium (machine readable storage medium) and perform any one or more of the methods discussed herein in accordance with several embodiments. By.

3 is a schematic diagram of various architectures for assisted VR effect energy threshold monitoring and/or threshold crossing notifications in accordance with the description herein.

4 is a diagram showing a flow of various threshold generations for monitoring a VR PM data program in accordance with the description herein, showing an example of a process for monitoring a VR energy measurement threshold and generating a notification when a threshold crossing or performance alert is detected.

5 is a block diagram of various systems for assisting threshold monitoring and/or notification operations for VNF-related VR PMs in accordance with the description herein.

6 is a flow diagram of various methods for assisting NM-based threshold monitoring operations in accordance with the description herein.

7 is a flow diagram of various methods for assisting threshold monitoring operations by EM in accordance with the description herein.

8 is a flow diagram of various methods for assisting threshold monitoring operations by VNFM in accordance with the description herein.

9 is a flow diagram of various methods for assisting threshold monitoring operations by VIM in accordance with the description herein.

310‧‧‧Network Manager (NM)

320‧‧‧Network Function Virtualization (NFV) Planner (NFVO)

330‧‧‧Network Element Manager (EM)

340‧‧‧VNF Manager (VNFM)

350‧‧‧Network Function Virtualization (NFV) Infrastructure (NFVI)

360‧‧‧Virtual Infrastructure Manager (VIM)

370 ₁ , 370 ₂ ‧‧‧Virtual Networking Function (VNF)

Claims (29)

A device configured to be used within a network manager (NM), comprising: a memory; and one or more processors configured to: make a decision, wherein the decision is A decision to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM) for deleting a first existing threshold to monitor a VNF related VR PM Deciding, or using a detail information of one or more existing thresholds to monitor a decision of the VNF-related VR PM; sending a request to an element manager (EM), wherein the request to the EM is: in response to the Determining to generate the new threshold for generating the new threshold to monitor the VNF-related VR PM request to the EM, in response to the decision deleting the existing threshold for the decision to delete to monitor the VNF-related VR Requesting one of the PMs to the EM, or in response to the decision to list the threshold identified by one of the threshold identifiers for obtaining the decision to one of the EM requests; and receiving a response from the EM , the response from the EM is: responding to the EM The request is a response from the EM indicating a result of a threshold generation for generating the request to the EM, and the request in response to the request to the EM is indicated by the request to the EM for deletion One of the threshold deletions results from one of the EM responses, or the request from the EM is the request from the EM for the request to the EM indicating the details of the one or more existing thresholds from the EM One responded. The device of claim 1, wherein the one or more processors are further configured to receive a VNF-related VR performance alert notification from the EM. The device of claim 1, wherein the request to the EM is the request to generate the EM. The device of claim 3, wherein the request to the EM includes an information target category (IOC) case indicating one or more of the one or more ManagedEntity cases (measurementTypes) to be monitored. List (iOCInstanceList) parameters. The device of claim 4, wherein the request to the EM includes an IOC name (iOCName) parameter indicating a ManagedEntity class name for each of the one or more ManagedEntity cases specified by the iOCInstanceList parameter . The device of claim 3, wherein the request to the EM includes a thresholdInfoList parameter indicating the new threshold for one or more particular measurementTypes. The device of claim 1, wherein the request to the EM is the request to delete the EM, and the request to the EM includes a monitor identity indicating a ThresholdMonitor to be stopped and removed (monitorId) parameter. The device of claim 1, wherein the request to the EM is the request to the EM for the list, and the request to the EM includes a monitor identity list (monitorIdList) indicating the ThresholdMonitors to be listed )parameter. An apparatus configured to be used within an element manager (EM), comprising: a memory; and one or more processors configured to: receive from a network manager (NM) a first request, wherein the first request from the NM is to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM) from the NM a first request for deleting an existing threshold to monitor a first request from the NM of the VNF-related VR PM, or to list a threshold identified by a list of threshold identifiers from the NM Transmitting a second request to a VNF Manager (VNFM), wherein the second request to the VNFM is: responding to the first request from the NM being the one from the NM for generating A second request to generate the new threshold to monitor the VNF-related VR PM to the VNFM, in response to the first request from the NM being the first request from the NM for deletion a second request to remove the existing threshold to monitor the VNF-related VR PM to the VNFM, Responding to the first request from the NM being a second request to the VNFM for listing the first request from the NM for listing the thresholds identified by the list of threshold identifiers; Receiving a first response from the VNFM, wherein the first response from the VNFM includes: responding to the second request to the VNFM as the second request to the VNFM for generating, the one or more thresholds One or more identifiers are generated, and in response to the second request to the VNFM being the second request to the VNFM for deletion, one or more identifiers are deleted, Or responding to the second request to the VNFM as a detail of one or more thresholds for listing the second request to the VNFM; and transmitting a second response to the NM, wherein the first to the NM a second response indication: a result of the first request to generate the new threshold from the first response threshold of the VNFM generated by the one or more identifiers including the one or more thresholds Responding to the one or more identifiers including the one or more thresholds Deleting the first response threshold from the VNFM to delete one of the results of the first request for the existing threshold, or responding to the first response threshold from the VNFM containing the details of one or more thresholds The details of the one or more thresholds. The device of claim 9, wherein the one or more processors are further configured to: receive a notification from a VNF manager (VNFM) that a threshold has been crossed on the VNF-related VR PM; By adding a VNF-related VR performance alert to an alert list, a decision is made to generate a performance alert; and a VNF-related VR performance alert notification is sent to the NM. The device of claim 9, wherein the first request from the NM is the first request from the NM to be generated, and the second request to the VNFM is the one to be generated to the VNFM Two requests. The device of claim 11, wherein the second request to the VNFM includes a sourceSelector parameter indicating one or more measurement types. The device of claim 11, wherein the second request to the VNFM includes a PerformanceMetric parameter, a ThresholdType parameter, and a thresholdDetails parameter, which are generated to monitor the one or more of the ones specified in the sourceSelector parameter The new threshold for the type of measurement. The device of claim 11, wherein the first response from the VNFM includes a threshold identity (thresholdId) parameter indicating one of the new thresholds that have been generated. The device of claim 11, wherein the second response to the NM includes a monitor identity parameter indicating a unique identifier of a ThresholdMonitor associated with the new threshold, and including a "Success" A state parameter of a value. The device of claim 9, wherein the first request from the NM is the first request from the NM for deletion, and the second request to the VNFM is the first to delete the VNFM The second request, and wherein the second response to the NM includes a status parameter having a value of "Success", "Failure", or "PartialSuccess". The device of claim 9, wherein the first request from the NM is the first request from the NM for the list, and the second request to the VNFM is the one to the VNFM for the list The second request, and wherein the second response to the NM includes a monitor information list (monitorInfoList) parameter, the monitor information list (monitorInfoList) parameter includes a feedback information corresponding to the ThresholdMonitors matching input standard. A device configured to be internal to a Virtualized Network Function (VNF) Manager (VNFM), comprising: a memory; and one or more processors configured to: receive from a component One of the managers (EM) requests, wherein the request from the EM is to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) energy measurement (PM) from One of the EM requests to delete an existing threshold to monitor a request from the EM for the VNF-related VR PM, or to request a list of thresholds identified by a list of threshold identifiers from the EM; And sending a response to the EM, wherein the response to the EM indicates that one or more identifiers are one or more identifiers in response to the request from the EM being the request from the EM for the request Generating, in response to the request from the EM being the request for deletion from the EM, one or more identifiers are deleted, or the request from the EM is for the list The details of one or more thresholds from the request for the EM. The device of claim 18, wherein the one or more processors are further configured to detect that the VNF-related VR PM has crossed a first threshold. The device of claim 19, wherein the one or more processors are further configured to transmit to the VNF-related VR PM that the first threshold has been notified to the EM across one of the first thresholds. The device of claim 20, wherein the notification includes a target instance identity (objectInstanceId) parameter identifying the first threshold. The device of claim 20, wherein the notification includes a thresholdId parameter, a crossingDirection parameter, a performanceMetric parameter, and a performanceValue parameter indicating that the first threshold has been crossed. The device of claim 19, wherein the one or more processors are further configured to detect that the VR PM has crossed the threshold based on a threshold received from a Virtualized Infrastructure Manager (VIM) The first existing threshold. The device of claim 18, wherein the one or more processors are further configured to: send an additional request to a Virtualized Infrastructure Manager (VIM), wherein the additional request indication to the VIM is responsive to The request of the EM is the request from the EM for generating the request from the EM, indicating that the request from the EM is for the request for deletion from the EM. The request from the EM to delete the request from the EM, or the request to respond to the request from the EM as a list for the request from the EM for the list; and receiving from the virtualization base An additional response from one of the Architecture Managers (VIMs), wherein the additional response from the VIM is responsive to the additional request to the VIM indicating the request from the EM to generate the request from the EM for generation a result of the request, in response to the additional request to the VIM indicating the request from the EM for deletion of the request for deletion, or the response to the additional request indication to the VIM To produce The request from the EM for the list is indicated from the request of the EM. The device of claim 18, wherein the request from the EM is the request from the EM for generation, and the response to the EM includes a threshold indicating one of the new thresholds that have been generated Identity (thresholdId) parameter. A device that is configured to be employed within a virtualized infrastructure manager (VIM), comprising: a memory; and one or more processors configured to: process functions from a virtualized network One of the (VNF) Manager (VNFM) requests, wherein the request from the VNFM is associated with a threshold monitoring of a Virtualized Network Function (VNF) related Virtualization Resource (VR) Effective Energy Measurement (PM), wherein The request from the VNFM is used to generate a new threshold to monitor the VNF-related VR PM request from one of the VNFMs to delete one of the existing thresholds for monitoring a set of the VNF-related VR PMs. a threshold request from one of the VNFMs, or a request from one of the VNFMs to list one or more existing thresholds of the set by a list of one of the threshold identifiers; in response to the request from the VNFM Requesting, in response to a request from the VNFM that the request is generated from the VNFM to generate the new threshold to monitor the VNF-related VR PM, in response to the request from the VNFM being Used to delete from the V The NFM deletes the indicated existing threshold in the existing threshold of the set, or generates a monitoring of the VNF-related VR PM in response to the request from the VNFM being the request from the VNFM for the list a list of existing thresholds of the two sets; and transmitting a response to the VNFM, the response indicating the result of the request from the VNFM for generating the new threshold, the indication responding to the deletion of the indicated threshold The result of the request from the VNFM to delete, or the result of the request from the VNFM for generating a list in response to the generation of the list. The device of claim 26, wherein the one or more processors are further configured to transmit a threshold crossing the notification to the VNFM associated with an existing threshold across which one of the set of existing thresholds has been crossed, wherein The threshold crosses the notification indicating an associated identifier for one of the existing thresholds that have been crossed. The device of claim 27, wherein the one or more processors are further configured to detect a threshold crossing associated with the existing threshold that has crossed, and wherein the one or more processors are The match is generated in response to the threshold crossing to generate the threshold across the notification. The device of claim 27, wherein the one or more processors are further configured to receive an additional threshold crossing notification from one of a Network Function Virtualization Infrastructure (NFVI), and one or more of the ones The processor is configured to generate the threshold crossing notification in response to the additional threshold received from the NFVI crossing the notification.