Enhanced exposure of mobile network performance metrics data to third parties

Abstract

Enhanced exposure of mobile network performance metrics data to third parties is provided. A method for enhanced exposure of mobile network performance metrics data to third parties may include receiving, from a management service consumer configured for another network, a request for performance measurement metrics related to a service provided by the management service consumer. The method may also include extracting input attributes from the request, translating the input attributes into performance measurement metrics for the network, and transmitting, to the management service consumer, information related to performance measurement metrics.

Description

TITLE:ENHANCED EXPOSURE OF MOBILE NETWORK PERFORMANCE METRICS DATA TO THIRD PARTIESTECHNICAL FIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR) access technology, or 5G beyond, or sixth generation (6G) access technology or other communications systems. For example, certain example embodiments may relate to enhanced exposure of mobile network performance metrics data to third parties.BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE- A), MulteFire, LTE-A Pro, fifth generation (5G) radio access technology or new radio (NR) access technology and / or sixth generation (6G) radio access technology. Fifth generation (5G) and sixth generation (6G) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G and 6G network technology is mostly based on new radio (NR) technology, but the 5G / 6G (or NG) network can also build on E-UTRAN radio. It is estimated that NR may provide bitrates on the order of 10-20 Gbit / s or higher and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low- latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (IoT).SUMMARY:

[0003] Various exemplary embodiments may provide an apparatus configured for a network comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive, from a management service consumer configured for another network, a request for performance measurement metrics related to a service provided by the management service consumer. The apparatus may also be caused to extract input attributes from the request and translate the input attributes into performance measurement metrics for the network, and transmit, to the management service consumer, information related to performance measurement metrics.

[0004] Certain exemplary embodiments may provide a method comprising receiving, from a management service consumer configured for another network, a request for performance measurement metrics related to a service provided by the management service consumer. The method may also comprise extracting input attributes from the request and translating the input attributes into performance measurement metrics for a network different from the other network, and transmitting, to the management service consumer, information related to performance measurement metrics.BRIEF DESCRIPTION OF THE DRAWINGS:

[0005] For proper understanding of example embodiments, reference should be made to the accompanying drawings, as follows:

[0006] FIG. 1 illustrates an example of a diagram for a configuration of network interactions, according to various exemplary embodiments;

[0007] FIG. 2 illustrates an example of a signal diagram for one or more procedures, according to certain exemplary embodiments;

[0008] FIG. 3 illustrates an example of a diagram of an information model, according to some exemplary embodiments;

[0009] FIG. 4 illustrates an example of a diagram of an information model for inheritance relations, according to various exemplary embodiments;

[0010] FIG. 5 an example of a flow diagram of a method, according to some exemplary embodiments; and

[0011] FIG. 6 illustrates a set of apparatuses, according to various exemplary embodiments.DETAILED DESCRIPTION:

[0012] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. The following is a detailed description of some exemplary embodiments of systems, methods, apparatuses, and non-transitory computer program products for enhanced exposure of 3rdgeneration partnership project (3 GPP) mobile network performance metrics data to third parties. Although the devices discussed below and shown in the figures refer to 5G / 6G or Next Generation NodeB (gNB) network entities and / or devices and user equipment (UE) devices, this disclosure is not limited to only network entities / devices and UEs.

[0013] It may be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Different reference designations from multiple figures may be used out of sequence in the description, to refer to a same element to illustrate their features or functions. If desired, the different functions or procedures discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the following description should be considered as illustrative of the principles andteachings of certain example embodiments, and not in limitation thereof.

[0014] 3GPP has defined specifications for interactions between non-3GPP supported management and network services and 3GPP supported management and network services. These non-3GPP management and network services may be implemented by network entities referred to as non- 3 GPP management service (MnS) consumers. One issue with existing 3 GPP technologies may be that non-3GPP MnS consumers may include a significant portion of the non-3GPP network operator’s consumers, which may not have the technical abilities needed to manage and operate the network. However, these MnS consumers may still desire to receive information about the performance of one or more network instances supporting one or more management and network services. It may be desirable for the network to enable these non-3GPP MnS consumers to request and receive performance metrics data related to one or more management and network services.

[0015] 3GPP has defined mechanisms by which an authorized 3GPP management consumer may request and retrieve performance measurement (PM) metrics data from the 3GPP management system. These mechanisms may provide that the authorized 3GPP management consumer may request and receive PM data by creating performance metric processing (jobs) by identifying the management service in charge of the PM metrics, the associated network functions and the granularity of the reporting period. The 3GPP management system may be triggered to generate the PM metrics using the associated network functions and may transmit the PM metrics data to the 3GPP management consumer every requested reporting period. Further, the 3 GPP management consumer may decide to monitor and control the instantiated PM processors / jobs by specifying thresholds for specific PM metrics data and generating a list of available PM metrics data. The 3GPP management consumer may also decide to stop monitoring PM thresholds and / or receiving PM metrics at any time.

[0016] The non-3GPP MnS consumer may desire or require that PM metric data be collected from one or more geographical areas or regions of interest that corresponds to geographical areas or regions served by one or more management services and network functions (which are managed through their corresponding managed elements or objects). However, the non-3GPP MnS consumer may not always know the geographical area, or the geographical area may change frequently. For some vertical services related to communication and transport services, the applicable geographical area may change frequently or significantly enough that the non-3GPP MnS consumer may not be strictly interested in a single geographical area and may desire data from multiple geographical areas. As a result, the non-3GPP MnS consumer may desire performance data related to a specific service instead of a specific geographical area.

[0017] The non-3GPP MnS consumer may desire to identify a network service, such as a management service in charge of producing PM-related data, and the specific network function(s) corresponding to the service where the PM generation may be performed, such that the non-3GPP MnS consumer may be overwhelmed with too much information from the network. The non- 3GPP MnS consumer may also be unable to sufficiently control the instantiated processes / jobs for the PM metrics. The non-3GPP MnS consumer may not desire to know the network resource model of a mobile network operator (MNO) to use the existing 3 GPP mechanisms to filter out relevant information for the service. Some of the non-3GPP MnS consumers using network services, such as communication services, may not have sufficient knowledge or sophistication to identify and collect PM metric data related to a service owned by the non-3GPP MnS consumer.

[0018] The MNO may desire to expose its management services and network functions to the non-3GPP MnS consumers. However, MNOs may not want to directly expose their management services and objects to non-3GPP MnSconsumers and may rather have an intermediate service / layer as an intermediary to enable these interactions between MNOs and non-3GPP MnS consumers.

[0019] Various exemplary embodiments may provide technological advantages to support one or more procedures for non-3GPP MnS consumers to request and receive network performance metrics data by specifying a network (e.g., communication) service or an instance of the service, such as, for example, a network slice. Certain exemplary embodiments may provide a management data collection function performed by a network entity to enable matching management data (e.g., network measurement and key performance indicators (KPIs)) and their corresponding management services to, for example, geographical areas or regions. For example, in a certain geographical area, the management data collection function may match the geographical area to one or more network and management functions and / or services and may request or collect data from the identified network and management functions and / or services.

[0020] Some exemplary embodiments may provide advantages in which non- 3 GPP MnS consumers may be able to easily provide their requirements for PM metrics data and the MNO may translate these requirements accordingly. Various exemplary embodiments may propose one or more procedures for non-3GPP MnS consumers to easily define their requirements for PM metrics data and for the MNO to translate these requirements, which may also be referred to as vertical requirements, into the corresponding 3 GPP mechanisms for PM metrics monitoring and availability without directly exposing managed services and objects of the MNO to non-3GPP MnS consumers.

[0021] Various exemplary embodiments may provide a PM exposure management function (MnF) that may be configured to enable non- 3 GPP MnS consumers to easily define their requirements for PM metrics related to one or more services. The MnF may also translate these requirements withoutdirectly exposing services and objects of the 3GPP management system.

[0022] FIG. 1 illustrates an example of a diagram for a configuration of interactions between a non-3GPP MnS consumer 101 and an MnF 102, according to various exemplary embodiments. The MnF 102 may receive requirements for a service (e.g., vertical service) implemented by the non- 3GPP MnS consumer 101 from the non-3GPP MnS consumer 101. The MnF 102 may then translate these service requirements into their corresponding 3GPP management services, objects, operations, and / or notifications. The MnF 102 may then expose / transmit PM metrics data to the non-3GPP MnS consumer 101.

[0023] The MnF 102 may comprise a PM exposure MnS producer 103 and / or a PM exposure MnF 104, and / or a performance assurance MnS consumer 105. The MnF 102 may trigger the performance assurance MnS consumer 105 to create PM processes / jobs for one or more managed objects 106, such as NR cells, which provide PM metrics data back to the performance assurance MnS consumer 105 for exposure by the MnF 102 to the non-3GPP MnS consumer 101.

[0024] FIG. 2 illustrates an example of a signal diagram between a non-3GPP MnS consumer 201 and an MnF 202 for one or more procedures, according to various exemplary embodiments. The non-3GPP MnS consumer 201 may be a vertical service consumer and the MnF 202 may comprise a PM exposure MnS producer. At 210, the non-3GPP MnS consumer 201 may provide a request for abstract PM requirements to the PM exposure MnS producer of the MnF 202. At 220, the MnF 202 may translate the PM requirements into corresponding 3 GPP management services, objects, operations, and / or notifications. At 230, the MnF 202 may map the PM requirements of the vertical service of the non-3GPP MnS consumer 201 to corresponding managed objects and performance assurance MnS producers.

[0025] At 240, the MnF 202 may create, or trigger creation, of PM processes(jobs) on the performance assurance MnS producers. If the vertical service consumer indicates in the request a desire for threshold monitoring for one or more PM metrics, at 250, the MnF 202 may create threshold monitors on the corresponding performance assurance MnS producers. At 260, the MnF 202 may provide a response to the non-3GPP MnS consumer 201, which may include PM metrics data as a response to the request for abstract PM requirements.

[0026] At 270, if PM metrics have been successfully collected, the MnF 202 may provide one or more generated PM metrics to the non-3GPP MnS consumer 201, or at 280, if the PM metrics have not been successfully collected due to a failure, the MnF 202 may provide an error message to the MnF 202. Procedures 270 and / or 280 may be repeatedly performed in a loop at predetermined intervals for each reporting period, which may be set by the non-3GPP MnS consumer 201 in the request. At 290, the MnF 202 may provide one or more notifications for indicating that one or more PM thresholds have been exceeded or crossed when the MnF 202 is performing PM threshold monitoring.

[0027] Certain exemplary embodiments may provide that access to any of the services of a 3GPP management system, the non-3GPP MnS consumer may either perform an explicit or implicit authentication and authorization procedure with the PM exposure MnS producer of the MnF. The non-3GPP MnS consumer may need to be authenticated and authorized by the PM assurance MnS producer. This access control to the 3GPP management system may be performed indirectly through the PM exposure MnS producer to the PM assurance MnS producer. Upon successful authentication and authorization, the non-3GPP MnS consumer may proceed to providing the request for PM requirements to the PM exposure MnS producer of the MnF.

[0028] The request for PM requirements from the non-3GPP MnS consumer may state the requirements for PM metric data using simple and / or abstractstatements such as, for example, “I want the following performance metrics related to my service X every 5 minutes,” “I want the following performance metrics related to my slice Y every 2 minutes,” “I want the following performance metrics related to my service in this geographical region every 3 minutes,” “I want the following performance metrics related to my service Z every 10 minutes for the next 30 days,” and / or “I want to be informed every time the following performance metrics related to my service X exceed or go below the given thresholds.”

[0029] The request for PM requirements from the non-3GPP MnS consumer may include various information related to the abstract vertical requirements for PM metrics. As mentioned above, these abstract requirements for PM metrics data are sent by the non-3GPP MnS consumer to the PM exposure MnS producer of the MnF for translation. For example, the following Table1 provides non-limiting examples of the types of information related to the ab stract vertical requirements .[TABLE 1]

[0030] The PM exposure MnS producer of the MnF may, upon receiving the request for PM metrics data from the non-3GPP MnS consumer, extract relevant input attributes depending on the structure of the request and may perform translation of the input attributes of the PM requirements into corresponding 3 GPP management services, objects, operations, and / or notifications. For example, Table 2 below provides non-limiting examples of input attributes and how each input attribute is translated by the PM exposure MnS producer.[TABLE 2]

[0031] Upon translating the input attributes of the PM requirements and collecting the PM metrics data, the PM exposure MnF producer of the MnF may provide or output related information to the non-3GPP MnS consumer.For example, the related information provided / outputted may include an indication of whether the translation of the abstract PM requirements was successful or not, an indication of whether the corresponding PM processes / jobs was instantiated successfully or not, an indication that the PM metrics data was received and may be available for download according to the set reporting period, and / or one or more notifications on the outcome(s) of the PM threshold(s) monitoring according to the threshold(s) and related information provided in the request.

[0032] An exemplary implementation of various exemplary embodiments is provided to aid in the understanding of the invention. This exemplary implementation is not limiting and may include more, less, or different procedures than those described. The exemplary implementation may be directed to providing an improved network to support means to enable non- 3GPP MnS consumers to request and receive PM metrics data related to oneor more services.

[0033] The non-3GPP MnS consumer may need to identify the management service in charge of producing PM-related data and the specific network functions corresponding to their service, which is the network function where the PM generation may be performed. The non-3GPP MnS consumers may be advantageously able to provide or state their requirements for PM metrics data to avoid potential complications with PM metrics data requesting and collection and the control of instantiated jobs for the PM metrics.

[0034] Various exemplary embodiments may provide one or more requirements for the 3GPP management system to be able to achieve these advantages discussed herein. For example, the 3GPP management system may have the capability to enable non-3GPP MnS consumers to request PM metrics using abstract means or non-technical statements. Examples of abstract means may be a reference to the services and / or network slices associated to the non-3GPP MnS consumer. The 3GPP management system may have the capability to enable the non-3GPP MnS consumers to request PM metrics by specifying the geographical area or region of interest. The 3GPP management system may have the capability to enable the non-3GPP MnS consumers to express the granularity of collecting and reporting PM metrics data, such as a reporting period or time interval.

[0035] Certain exemplary embodiments may provide that the 3 GPP management system may have the capability, via an MnF, to translate the abstracted PM requirements from the non-3GPP MnS consumers into corresponding 3 GPP management services, objects, operations, and subscriptions associated with the vertical service of the non-3GPP MnS consumer. The 3 GPP management system may have the capability to trigger PM processes / jobs on the corresponding PM MnS service producers of the MnF and managed objects derived from the translation of the requirements for PM metrics data. The 3GPP management system may have the capability toinform the non-3GPP MnS consumer about events related to the instantiated PM exposure request or the PM jobs triggered or created in response to the request. The events may include, for example, notifications about issues with the vertical request, events about the success or failure of the creation of the PM jobs, notifications when the performance metrics data is ready for downloading, and / or notifications when one or more performance metrics has crossed the set PM thresholds. The 3GPP management system may have the capability to expose the generated PM metrics to the non-3GPP MnS consumer according to one or more characteristics of the request, such as according to a set reporting period. The 3 GPP management system may have the capability to enable the non-3GPP MnS consumer to request and be informed when one or more PM metrics related to its service or network slice cross a specified threshold.

[0036] To support the exposure of PM metrics data, some exemplary embodiments may provide a network entity in the form of an information object class (IOC) with properties of the PM exposure MnF. This may be referred to as an PMExposure to be name-contained in either a subnetwork, a ManagedFunction or a ManagementFunction. A list of PMs and / or thresholds for which reports may be needed may be added to the PMExposure. Certain attributes on the PMExposure, such as service and network slice identifiers, may indicate the need for PMs on objects supporting the service or network slice. The PM request from the non-3GPP MnS consumer may also include geographical area or regions of interest as an indication of the area covering the managed objects for which PMs and thresholds may be needed. The request from the non-3GPP MnS consumer may include an attribute that characterizes a reporting period which may be required for PM monitoring. The reporting period may be defined by a time window over which the one or more PMs should be reported, either intermittently or continuously.

[0037] FIG. 3 illustrates an example of a diagram of an information model forPM exposure, according to certain exemplary embodiments. A proxy class of a managed entity 310 may be defined to represent one or more IOCS 320 that may be name-contained in a subnetwork, a ManagedFunction and / or a ManagementFunction. FIG. 3 illustrates an example of a class diagram of the IOC 320 of PM exposure, according to various exemplary embodiments. The class diagram may indicate where the IOC could be instantiated from, as a name- containment property. The IOC may be instantiated from, for example, a subnetwork, a managed function, or a management function.

[0038] FIG. 4 illustrates an example of a diagram of an information model for inheritance relations of PM exposure, according to some exemplary embodiments. The IOC for the PM exposure 420 may inherit information related to an IOC of a ManagedFunction 410. FIG. 4 illustrates an example of an IOC which may inherit one or more properties or attributes from, for example, the IOC of the ManagedFunction 410.

[0039] The IOC may represent the properties of PMExposure in the class definition for PMExposure «IOC». The PMExposure IOC may include, for example, the following attributes in Table 3.[TABLE 3]

[0040] Some exemplary embodiments may provide that the request from the non-3GPP MnS consumer may define one or more attributes in the request. For example, Table 4 provides various non-limiting examples of attributes andtheir corresponding documentation and allowed values and properties.[TABLE 4]

[0041] The request from the non-3GPP MnS consumer may define conditions for certain conditional attributes. For example, Table 5 provides non-limiting examples of the conditions for certain conditional attributes.[TABLE 5]

[0042] FIG. 5 illustrates an example flow diagram of a method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 5 may be performed by a network element, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR. For instance, in an exemplary embodiment, the method of FIG. 5 may be performed by network node or network entity, such as an MnF, similar to apparatus 610 illustrated in FIG. 6.

[0043] According to various exemplary embodiments, the method of FIG. 5 may include, at 510, receiving, from a non-3GPP MnS consumer configured for another, non-3GPP network, a request for PM metrics related to a service provided by the MnS consumer. At 520, the method may include extracting input attributes from the request and translating the input attributes into PM metrics for the network. At 530, the method may further include transmitting, to the MnS consumer, information related to PM metrics.

[0044] Certain exemplary embodiments may provide that the request comprises an indication of the service and network slices associated with theMnS consumer. The request may comprise an indication specifying a geographical area or geographical region of interest for the service provided by the MnS consumer. The request may comprise a periodicity for the apparatus to transmit the information related to PM metrics.

[0045] Some exemplary embodiments may provide that the translating the input attributes into PM metrics for the network comprises mapping the input attributes to management services, objects, operations, and subscriptions in the network associated with the service, and / or mapping geographical area or geographical region of interest for the service to cells of the network. Certain exemplary embodiments may provide that the transmitted information related to PM metrics comprises an indication of whether or not the translating of the input attributes into PM metrics has been successful, an indication of whether or not one or more PM processes / jobs have been instantiated successfully, and / or an indication that the PM metrics have been obtained and are available to provide to the MnS consumer. Various exemplary embodiments may provide that the request comprises a request for one or more PM thresholds. The transmitted information related to PM metrics may comprise one or more notifications on one or more results of a monitoring of the one or more PM thresholds.

[0046] Some exemplary embodiments may provide that the method further includes triggering PM processes / jobs on corresponding service producers and managed objects of the network derived from the translating the input attributes into PM metrics. The method may also include monitoring one or more PM thresholds based on threshold values provided by the MnS consumer and notifying the MnS consumer when the PM metrics corresponding to the one or more PM thresholds exceed the one or more PM thresholds. Certain exemplary embodiments may provide that the method includes transmitting, to the MnS consumer at predetermined periodic intervals, the PM metrics, or an error message when translating of the input attributes is unsuccessful, or anerror message when one or more PM processes have not been successfully instantiated, or a notification that one or more PM thresholds has been exceeded by the PM metrics.

[0047] FIG. 6 illustrates apparatuses 610 and 620 according to various exemplary embodiments. In the various exemplary embodiments, apparatus 610 may be an element in a network or associated with the network, or a network entity, such as an MnF. MnF 102 / 202 may be examples of apparatus 610 according to various exemplary embodiments as discussed above. It should be noted that one of ordinary skill in the art would understand that apparatus 610 may include components or features not shown in FIG. 6. Further, the apparatus 620 may be an element in a network or associated with the network or a network entity, such as a non-3GPP MnS consumer. Non- 3 GPP MnS consumer 101 / 201 may be examples of apparatus 620 according to various exemplary embodiments as discussed above. It should be noted that one of ordinary skill in the art would understand that apparatus 620 may include components or features not shown in FIG. 6.

[0048] According to various exemplary embodiments, the apparatuses 610 and / or 620 may include one or more processors, one or more computer- readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and / or a user interface. In some exemplary embodiments, apparatuses 610 and / or 620 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technologies.

[0049] As illustrated in the example of FIG. 6, apparatuses 610 and / or 620 may include or be coupled to processors 612 and 622, respectively, for processing information and executing instructions or operations. Processors 612 and 622 may be any type of general or specific purpose processor. In fact, processors 612 and 622 may include one or more of general -purpose computers, specialpurpose computers, microprocessors, digital signal processors (DSPs), field- programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 612 (and 622) for each of apparatuses 610 and / or 620 is shown in FIG. 6, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatuses 610 and / or 620 may include two or more processors that may form a multiprocessor system (for example, in this case processors 612 and 622 may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled to, for example, form a computer cluster.

[0050] Processors 612 and 622 may perform functions associated with the operation of apparatuses 610 and / or 620, respectively, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatuses 610 and / or 620, including processes illustrated in FIGs. 1-5.

[0051] Apparatuses 610 and / or 620 may further include or be coupled to memory 614 and / or 624(intemal or external), respectively, which may be coupled to processors 612 and / or 622, respectively, for storing information and instructions that may be executed by processors 612 and 622. Memory 614 (and memory 624) may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and / or removable memory. For example, memory 614 (and memory 624) can be comprised of any combination of random access memory (RAM), read only memory(ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 614 and memory 624 may include program instructions or computer program code that, when executed by processors 612 and 622, enable the apparatuses 610 and / or 620 to perform tasks as described herein.

[0052] In certain example embodiments, apparatuses 610 and / or 620 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processors 612 and 622 and / or apparatuses 610 and / or 620 to perform any of the methods illustrated in FIGs. 1-5.

[0053] In some exemplary embodiments, apparatuses 610 and / or 620 may also include or be coupled to one or more antennas 615 and 625, respectively, for receiving a downlink signal and for transmitting via an uplink from apparatuses 610 and / or 620. Apparatuses 610 and / or 620 may further include transceivers 616 and 626, respectively, configured to transmit and receive information. The transceivers 616 and 626 may also include a radio interface (for example, a modem) respectively coupled to the antennas 615 and 625. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, or the like. The radio interface may include other components, such as filters, converters (for example, digital-to- analog converters or the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, or the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.

[0054] For instance, transceivers 616 and 626 may be respectively configuredto modulate information on to a carrier waveform for transmission by the antenna(s) 615 and 625, and demodulate information received via the antenna(s) 615 and 625 for further processing by other elements of apparatuses 610 and / or 620. In other example embodiments, transceivers 616 and 626 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatuses 610 and / or 620 may include an input and / or output device (I / O device). In certain example embodiments, apparatuses 610 and / or 620 may further include a user interface, such as a graphical user interface or touchscreen.

[0055] In certain example embodiments, memory 614 and memory 624 may store software modules that provide functionality when executed by processors 612 and 622, respectively. The modules may include, for example, an operating system that provides operating system functionality for apparatuses 610 and / or 620. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatuses 610 and / or 620. The components of apparatuses 610 and / or 620 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, apparatus 610 may optionally be configured to communicate with apparatus 620 via a wireless or wired communications link 630 according to any radio access technology, such as NR.

[0056] According to certain example embodiments, processors 612 and 622, and memory 614 and 624 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 616 and 626 may be included in or may form a part of transceiving circuitry.

[0057] For instance, in certain exemplary embodiments, the apparatus 610 may be controlled by the memory 614 and the processor 612 to receive, from a MnS consumer configured for another network, a request for PM metricsrelated to a service provided by the management service consumer. The apparatus 610 may also be controlled to extract input attributes from the request and translate the input attributes into PM metrics for the network and transmit, to the MnS consumer, information related to PM metrics.

[0058] In some exemplary embodiments, an apparatus (e.g., apparatus 610 and / or apparatus 620) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing the performance of the operations.

[0059] Various exemplary embodiments may be directed to an apparatus, such as apparatus 610, that includes means for receiving, from an MnS consumer configured for another network, a request for PM metrics related to a service provided by the MnS consumer. The apparatus 610 may also include means for extracting input attributes from the request and translate the input attributes into PM metrics for the network and means for transmitting, to the MnS consumer, information related to PM metrics.

[0060] As used herein, the term “circuitry” may refer to hardware-only circuitry implementations (for example, analog and / or digital circuitry), combinations of hardware circuits and software, combinations of analog and / or digital hardware circuits with software / firmware, any portions of hardware processor(s) with software, including digital signal processors, that work together to cause an apparatus (for example, apparatus 610 and / or 620) to perform various functions, and / or hardware circuit(s) and / or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term “circuitry” may also cover an implementation of merely a hardware circuit or processor or multiple processors, or portion of a hardware circuit or processor, and the accompanying software and / or firmware. The term circuitry may also cover, for example, a basebandintegrated circuit in a server, cellular network node or device, or other computing or network device.

[0061] A computer program product may include one or more computerexecutable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain example embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0062] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and / or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0063] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (for example, apparatuses 610 and / or 620), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0064] According to certain example embodiments, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[0065] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “an example embodiment,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “an example embodiment,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. Further, the terms “cell”, “node”, “gNB”, or other similar language throughout this specification may be used interchangeably.

[0066] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0067] One having ordinary skill in the art will readily understand that the disclosure as discussed above may be practiced with procedures in a different order, and / or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the disclosure has beendescribed based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. Although the above embodiments refer to 5G NR and LTE technology, the above embodiments may also apply to any other present or future 3 GPP technology, such as LTE-advanced, and / or fourth generation (4G) and / or sixth (6G) technology.

[0068] Partial Glossary:

[0069] 3 GPP 3rd Generation Partnership Project

[0070] 5G 5th Generation

[0071] 6G 6thGeneration

[0072] DL Downlink

[0073] EMBB Enhanced Mobile Broadband

[0074] gNB 5G or Next Generation NodeB

[0075] ID Identifier

[0076] IOC Information Object Class

[0077] KPI Key Performance Indicator

[0078] LTE Long Term Evolution

[0079] MnF Exposure Management Function

[0080] MnS Management Service

[0081] MNO Mobile Network Operator

[0082] NR New Radio

[0083] PM Performance Measurement

[0084] UE User Equipment

[0085] UL Uplink

Claims

WE CLAIM:

1. An apparatus configured for a network comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a management service consumer configured for another network, a request for performance measurement metrics related to a service provided by the management service consumer; extract input attributes from the request and translate the input attributes into performance measurement metrics for the network; and transmit, to the management service consumer, information related to performance measurement metrics.

2. The apparatus according to claim 1, wherein the request comprises an indication of the service and network slices associated with the management service consumer.

3. The apparatus according to claim 1 or claim 2, wherein the request comprises an indication specifying a geographical area or geographical region of interest for the service provided by the management service consumer.

4. The apparatus according to any one of claims 1-3, wherein the request comprises a periodicity for the apparatus to transmit the information related to performance measurement metrics.

5. The apparatus according to any one of claims 1-4, wherein the translating the input attributes into performance measurement metrics for the network comprises: mapping the input attributes to management services, objects,operations, and subscriptions in the network associated with the service; or mapping geographical area or geographical region of interest for the service to cells of the network.

6. The apparatus according to any one of claims 1-5, wherein the transmitted information related to performance measurement metrics comprises an indication of whether or not the translating of the input attributes into performance measurement metrics has been successful.

7. The apparatus according to any one of claims 1-6, wherein the transmitted information related to performance measurement metrics comprises an indication of whether or not one or more performance measurement processes have been instantiated successfully by the apparatus.

8. The apparatus according to any one of claims 1-7, wherein the transmitted information related to performance measurement metrics comprises an indication that the performance measurement metrics have been obtained and are available to provide to the management service consumer.

9. The apparatus according to any one of claims 1-8, wherein: the request comprises a request for one or more performance measurement thresholds; and the transmitted information related to performance measurement metrics comprises one or more notifications on one or more results of a monitoring of the one or more performance measurement thresholds.

10. The apparatus according to any one of claims 1-9, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to:trigger performance measurement processes on corresponding service producers and managed objects of the network derived from the translating the input attributes into performance measurement metrics.

11. The apparatus according to any one of claims 1-10, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: monitor one or more performance measurement thresholds based on threshold values provided by the management service consumer; and notify the management service consumer when the performance measurement metrics corresponding to the one or more performance measurement thresholds exceed the one or more performance measurement thresholds.

12. The apparatus according to any one of claims 1-11, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: transmit, to the management service consumer at predetermined periodic intervals, the performance measurement metrics, or an error message when translating of the input attributes is unsuccessful, or an error message when one or more performance measurement processes have not been successfully instantiated, or a notification that one or more performance measurement thresholds has been exceeded by the performance measurement metrics.

13. A method, comprising: receiving, from a management service consumer configured for another network, a request for performance measurement metrics related to a service provided by the management service consumer;extracting input attributes from the request and translating the input attributes into performance measurement metrics for a network different from the other network; and transmitting, to the management service consumer, information related to performance measurement metrics.

14. The method according to claim 13, wherein the request comprises an indication of the service and network slices associated with the management service consumer.

15. The method according to claim 13 or claim 14, wherein the request comprises an indication specifying a geographical area or geographical region of interest for the service provided by the management service consumer.

16. The method according to any one of claims 13-15, wherein the request comprises a periodicity for the apparatus to transmit the information related to performance measurement metrics.

17. The method according to any one of claims 13-16, wherein the translating the input attributes into performance measurement metrics for the network comprises: mapping the input attributes to management services, objects, operations, and subscriptions in the network associated with the service; or mapping geographical area or geographical region of interest for the service to cells of the network.

18. The method according to any one of claims 13-17, wherein the transmitted information related to performance measurement metrics comprises an indication of whether or not the translating of the input attributesinto performance measurement metrics has been successful.

19. The method according to any one of claims 13-18, wherein the transmitted information related to performance measurement metrics comprises an indication of whether or not one or more performance measurement processes have been instantiated successfully by the apparatus.

20. The method according to any one of claims 13-19, wherein the transmitted information related to performance measurement metrics comprises an indication that the performance measurement metrics have been obtained and are available to provide to the management service consumer.

21. The method according to any one of claims 13-20, wherein: the request comprises a request for one or more performance measurement thresholds; and the transmitted information related to performance measurement metrics comprises one or more notifications on one or more results of a monitoring of the one or more performance measurement thresholds.

22. The method according to any one of claims 13-21, further comprising: triggering performance measurement processes on corresponding service producers and managed objects of the network derived from the translating the input attributes into performance measurement metrics.

23. The method according to any one of claims 13-22, further comprising: monitoring one or more performance measurement thresholds based on threshold values provided by the management service consumer; and notifying the management service consumer when the performance measurement metrics corresponding to the one or more performancemeasurement thresholds exceed the one or more performance measurement thresholds.

24. The method according to any one of claims 13-23, further comprising: transmitting, to the management service consumer at predetermined periodic intervals, the performance measurement metrics, or an error message when translating of the input attributes is unsuccessful, or an error message when one or more performance measurement processes have not been successfully instantiated, or a notification that one or more performance measurement thresholds has been exceeded by the performance measurement metrics.

Images