Network performance monitoring

Abstract

The example embodiments of the present disclosure relate to methods, equipment, devices and computer-readable storage media for network performance monitoring. In an example embodiment, the duration of a normal release call and the duration of an abnormal release call are monitored during a measurement period. Based on the duration of the monitored normal release call and the duration of the monitored abnormal release call, the average value of the duration of the monitored normal release call and the average value of the duration of the monitored abnormal release call are further determined. Then, the average value of the duration of the monitored normal release call and the average value of the duration of the monitored abnormal release call are sent.

Description

Technical Field

[0001] Example embodiments of the present disclosure relate generally to the field of communications, and in particular to methods, devices, apparatuses, and computer-readable storage media for network performance monitoring. Background Art

[0002] In the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), currently two types of key performance indicators (KPIs) are recommended for network performance monitoring, including the maintainability KPI specified in the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 32.425 and the maintainability KPI specified in 3GPP TS 32.450.

[0003] In 3GPP TS 32.425, it is recommended to use a maintainability KPI based on the E-UTRAN radio access bearer (E-RAB) and user equipment (UE) context release counter. This maintainability KPI is evaluated as the ratio of the number of abnormal release E-RABs (UE contexts) perceived by the end user as dropped to the total number of E-RABs (UE contexts). With the help of this KPI, it is possible to obtain the E-RAP drop ratio, which indicates the probability of E-RAB (UE context) drop. At the same time, in 3GPP TS 32.450, it is recommended to use another maintainability KPI, which is determined as the ratio of the active (with data activity at the time of drop) abnormal release E-RAB (UE context) to the total E-RAB (UE context) session time. Therefore, it is possible to obtain a value indicating the number of drops per second.

[0004] However, in some scenarios, neither type of KPI can accurately reflect the network performance experienced by end users. Sometimes, even if the KPIs used have the same value, end users may perceive network quality differently. Summary of the invention

[0005] In general, example embodiments of the present disclosure provide methods, devices, apparatuses, and computer-readable storage media for network performance monitoring.

[0006] In a first aspect, a method is provided. The method can be performed at a base station. In the method, the duration of a normal release call and the duration of an abnormal release call are monitored during a measurement period. Based on the monitored duration of the normal release call and the monitored duration of the abnormal release call, an average value of the monitoring duration of the normal release call and an average value of the monitoring duration of the abnormal release call are also determined. Then, the average value of the monitoring duration of the normal release call and the average value of the monitoring duration of the abnormal release call are sent to, for example, a management function or a function including a third-party tool.

[0007] In a second aspect, another method is provided. The method can be implemented at a management function. In the method, an average value of durations of normal released calls and an average value of durations of abnormal released calls monitored during a measurement period are received. Further, based on the average value of durations of normal released calls and the average value of durations of abnormal released calls, a relative difference between the durations of normal released calls and the durations of abnormal released calls is determined.

[0008] In a third aspect, a device is provided. The device comprises at least one processor and at least one memory, the memory comprising computer program code. The at least one memory and the computer program code are configured to cause the device to perform the method according to the first aspect with the at least one processor.

[0009] In a fourth aspect, another device is provided. The device includes at least one processor and at least one memory, the memory including computer program code. The at least one memory and the computer program code are configured to cause the device to perform the method according to the second aspect with the at least one processor.

[0010] In a fifth aspect, there is provided an apparatus comprising means for performing the method according to the first aspect.

[0011] In a sixth aspect, there is provided an apparatus comprising means for performing the method according to the second aspect.

[0012] In a seventh aspect, a computer-readable storage medium is provided, comprising program instructions stored thereon, wherein when the instructions are executed by a processor of a device, the device performs the method according to one or both of the first aspect and the second aspect.

[0013] It is to be understood that the summary section is not intended to identify key or essential features of the exemplary embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0015] Figure 1 illustrates example scenarios in which some example embodiments of the present disclosure may be implemented;

[0016] Figure 2 illustrates a flow chart of an example method for network performance monitoring according to some example embodiments of the present disclosure;

[0017] Figure 3Aillustrates example histograms of distribution of normal release call durations and distribution of abnormal release call durations according to some example embodiments of the present disclosure;

[0018] Figure 3B illustrates a specific scenario according to some example embodiments of the present disclosure, with two peaks in a histogram of the distribution of normal release call durations;

[0019] Figure 4 A flowchart illustrating an example method of network performance monitoring according to some other example embodiments of the present disclosure is illustrated;

[0020] Figure 5 illustrates a schematic diagram of an example 3D KPI model according to some example embodiments of the present disclosure, the model including KPI pyramids for normal release call duration and abnormal release call duration;

[0021] Figure 6 A flowchart of constructing a KPI cone for abnormal release call duration according to some example embodiments of the present disclosure is illustrated;

[0022] Figure 7 A schematic diagram of constructing a KPI cone for abnormal release call duration according to some example embodiments of the present disclosure is illustrated;

[0023] Figure 8 illustrates a flow chart for constructing a KPI cone for normal release call duration according to some example embodiments of the present disclosure;

[0024] Fig. 9 A signaling flow chart of an example method for network performance monitoring according to some example embodiments of the present disclosure is illustrated;

[0025] Fig.10 A flowchart illustrating an example method of network performance monitoring according to some other example embodiments of the present disclosure; and

[0026] Fig.11 A simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure is illustrated.

[0027] Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. DETAILED DESCRIPTION

[0028] The principles of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these example embodiments are described only for the purpose of illustration and to help those skilled in the art understand and implement the present disclosure without imposing any limitation on the scope of the present disclosure. In addition to the following, the disclosure described herein can also be implemented in various ways.

[0029] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0030] As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communication with each other or with a base station. Communication may involve the transmission and / or reception of wireless signals using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for transmitting information in the air. In some example embodiments, the UE may be configured to transmit and / or receive information without direct human-computer interaction. For example, when triggered by an internal or external event, or in response to a request from the network side, the UE may transmit information to the base station according to a predetermined schedule.

[0031] Examples of UE include, but are not limited to, smartphones, tablet computers with wireless support, tablet embedded equipment (LEE), tablet mounted equipment (LME), wireless customer premises equipment (CPE), sensors, metering equipment, personal wearable devices (such as watches), and / or vehicles capable of communication. For the purpose of discussion, some example embodiments will refer to UE being described as an example of a terminal device, and in the context of the present disclosure, the terms "terminal device" and "user equipment" (UE) may be used interchangeably.

[0032] As used herein, the term "base station" (BS) refers to a network device through which services can be provided to terminal devices communicating with the network. A base station may include any suitable device through which a terminal device or UE can access a communication network. Examples of base stations include repeaters, access points (APs), transmission points (TRPs), node Bs (NodeBs or NBs), evolved NodeBs (eNodeBs or eNBs), new radio (NR) NodeBs (gNBs), remote radio units (RRUs), radio heads (RHs), remote radio heads (RRHs), low power nodes such as femto, pico, etc.

[0033] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0034] (a) pure hardware circuit implementation (such as implementation in analog and / or digital circuitry only) and

[0035] (b) a combination of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware and (ii) any portion of hardware processor(s) and software (including digital signal processor(s), software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions) and

[0036] (c) Hardware circuits and / or processors, such as microprocessors or portions of microprocessors, that require software (e.g., firmware) to operate, but where the software may not be present, the software may not be required to operate.

[0037] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers only an implementation of a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example and if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit of a mobile device or a similar integrated circuit in a server, cellular base station or other computing or base station.

[0038] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and variations thereof should be interpreted as open terms meaning "including but not limited to". The term "based on" should be interpreted as "based at least in part on". The terms "one embodiment" and "an embodiment" should be interpreted as "at least one embodiment". The term "another embodiment" should be interpreted as "at least one other embodiment". Other definitions, both explicit and ambiguous, may be included below.

[0039] As used herein, the terms "first", "second", etc. may be used to describe various elements in this article, and these elements should not be limited to these terms. These terms are only used to distinguish different elements. For example, without departing from the scope of the exemplary embodiment, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more listed items.

[0040] In E-UTRAN, two types of KPIs are currently recommended for network performance monitoring, one can provide an E-RAB drop ratio indicating the probability of an E-RAB (UE context) drop, and the other can provide the number of drops per second. However, in some scenarios, these KPIs cannot accurately reflect the network performance experienced by the end user.

[0041] The voice service, which is most sensitively perceived by the end user, can be taken as an example. It can be assumed that two cells have the same E-RAB drop ratio of 90%, but in the first cell, the call is dropped and its duration is 99% of the expected call duration, while in the second cell, the call is also dropped and its duration is only 40% of the expected call duration. In this scenario, the end user will feel the voice service completely differently. In the first cell, almost all calls are completed by the end user, so the end user has a high probability of not making additional call requests; on the contrary, in the second cell, the call only lasts 40% of the expected call duration, so the end user has a high probability of making a second call to the same called party.

[0042] In this case, additional information is needed about which part of the expected call duration was performed when the call was dropped in order to closely monitor the end-user perception. In addition, it also helps in network performance optimization because for the example scenario, the second cell needs network performance optimization more urgently than the first cell because the call in the second cell only lasted 40% of the expected call duration.

[0043] The example embodiments of the present disclosure provide a novel network performance monitoring solution. In the solution provided herein, the duration of both normal release calls and abnormal release calls are monitored, and the relative difference between the normal call duration and the abnormal call duration can be calculated as a new retainability. With the help of the new retainability KPI, the end user perception can be closely monitored and network performance optimization can be facilitated.

[0044] Hereinafter, the solution proposed in the present disclosure will also be described in detail with reference to the accompanying drawings. However, it should be appreciated that the following embodiments are given for illustrative purposes only and the present disclosure is not limited thereto. It should also be noted that the embodiments of the present disclosure are mainly described with reference to E-UTRAN; however, the present disclosure is not limited thereto and may also be applied to any other technology, such as a fifth generation (5G) new radio (NR) system.

[0045] Figure 1 An example scenario 100 is illustrated in which an example embodiment of the present disclosure may be implemented; the environment 100 (which may be part of a communication network) includes a terminal device 105 and a base station 110. It is to be understood that one base station and three terminal devices are shown in the environment 100 for illustrative purposes only and do not impose any limitation on the scope of the present disclosure. Any suitable number of base stations and terminal devices may be included in the environment 100.

[0046] As shown, several terminal devices 105 are located in a cell 115, which are served by a base station 110. Each terminal device 105 can communicate with the base station 110 or with another terminal device directly or through the base station 110. Communications may follow any suitable communications standards or protocols that already exist or will be developed in the future, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Fifth Generation (5G) New Radio (NR), Wireless Fidelity (Wi-Fi) and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employ any suitable communications technology, including, for example, Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), Bluetooth, ZigBee and Machine Type Communication (MTC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Ultra-Reliable Low Latency Communication (URLLC), Carrier Aggregation (CA), Dual Connectivity (DC) and New Radio Unlicensed (NR-U) technology.

[0047] As shown, in the environment 100, the base station 110 can communicate with the Evolved Packet Center (EPC) 120 to provide services to the terminal device 105. The base station 110 can also communicate with the management function 130. The management function 130 can be, for example, an element management system (EMS) / network management system (NMS), or alternatively another functionality, including a third tool, such as a network management tool (e.g., NetAct commercially available from Nokia Corporation) or a real-time network analysis tool (e.g., Traffica commercially available from Nokia Corporation). The solution provided in the present disclosure can be implemented at the base station 110 and the management function 130.

[0048] It is to be understood that for the purpose of illustration, Figure 1 One base station is illustrated, in communication with the management function 130, without limiting the scope of the present disclosure. The management function 130 may be in communication with a large number of base stations to monitor network performance across multiple cells.

[0049] Figure 2 A signaling flow chart of an example method of network performance monitoring according to some example embodiments of the present disclosure is illustrated. The method 200 may be performed at a base station (such as an eNB or gNB) or any suitable network device suitable for monitoring the release of a call.

[0050] like Figure 2As shown in, first in block 210, during the measurement period, the duration of the normal release call and the duration of the abnormal release call are monitored. In an embodiment of the present disclosure, the base station can monitor both the duration of the normal release call and the abnormal release call, instead of only counting the abnormal release call.

[0051] In some embodiments of the present disclosure, each duration in the duration of a normal release call is measured from the time point when the call is successfully established until the call is released normally, and each duration in the duration of an abnormal release call is measured from the time point when the call is successfully established until the call is released abnormally. For example, for an E-UTRAN system, each duration sample can be measured from the time point when a quality of service (QoS) class identifier (QCI) 1 E-RAB has been successfully established through an initial context setup or an additional E-RAB setup procedure until the E-RAB is released by a release procedure initiated by an eNB or an evolved packet center (EPC) (e.g., according to the procedure defined in 3GPP TS 36.413). For an NR system, each duration sample can be measured from the time point when a QF11 QoS process has been successfully established through an initial context setup or an additional QF11 QoS process setup procedure until the time point when the QF11 QoS process is released by a release procedure initiated by a gNB or a next generation core (NGC) (e.g., according to the procedure defined in 3GPP TS 36.340).

[0052] In some embodiments of the present disclosure, at least one of the radio link failure (RLT) time period and the inactivity time period of the observed terminal user is excluded from monitoring. Specifically, the timer period associated with the running RLF timer should be excluded from the call duration because they do not represent any active call time. In addition, for cells with poor radio quality, the time period associated with this RLF timer may account for a non-negligible part of the total call duration, so it may distort the terminal user's perception. The same is true for the user inactivity timer operation. Typically, when the call is completed, the release of the QCI1 E-RAB is immediately completed from the EPC side, but in some cases, the user inactivity timer may be started on the base station side, and the QCI1 E-RAB is released only after the expiration of this user inactivity timer. Therefore, the observed inactivity time period of the terminal user can also be excluded from the call duration.

[0053] like Figure 2As shown in , in block 220, an average value of the monitoring duration of the normal release call and an average value of the monitoring duration of the abnormal release call are determined. In particular, the average value of the monitoring duration of the normal release call can be determined as the arithmetic mean of the samples (QCI1 E-RAB) of the normal release call at the end of the measurement period. Similarly, the average value of the monitoring duration of the abnormal release call can be determined as the arithmetic mean of the samples (QCI1 E-RAB) of the abnormal release call at the end of the measurement period.

[0054] In block 230, the average value of the monitoring duration of abnormal released calls and the average value of the monitoring duration of normal released calls can be sent, for example, to a management function. In other words, these determined average values ​​can be provided to the management function for further processing, such as determining a new maintainability KPI. For example, the relative difference between the normal call release duration and the abnormal call release duration can also be determined, as will be described below.

[0055] In some embodiments of the present disclosure, the base station can also determine the distribution of normal released call durations and the distribution of abnormal released call durations in multiple call duration time intervals based on the monitoring duration of normal released calls and the monitoring duration of abnormal released calls within the measurement period, and then the base station can transmit the distribution of normal released call durations and the distribution of abnormal released call durations to the management function.

[0056] For example, the call duration may be divided into a plurality of call duration time intervals. The number of call duration time intervals and their widths may be predetermined values ​​or may be configured by a network operator. For a normal release call, the base station may count the number (quantity, frequency) of normal release calls within each call duration time interval, thereby obtaining a distribution of the duration of the normal release call. Similarly, the base station may count the number (quantity, frequency) of abnormal release calls within each call duration time interval, thereby obtaining a distribution of the duration of the abnormal release call.

[0057] Preferably, the two distributions can be represented by two histograms. The distribution of normal release call duration can be represented by a first histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of normal release calls within the corresponding call duration time interval. The distribution of abnormal release call duration can be represented by a second histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of abnormal release calls within the corresponding call duration time interval.

[0058] For illustrative purposes, Figure 3ATwo histogram functions of the duration of normal release call and abnormal release call are illustrated, which can be displayed at the management function. As shown in the figure, the distribution of the abnormal call duration is indicated by the top histogram function, and the distribution of the normal call duration is indicated by the following histogram function. Each histogram function includes the bins of the configured number, and each bin is used to show the number (quantity or frequency) of the call duration (Y axis), and these call durations all fall in the configuration bin width (X axis) relevant to the call duration. The number of bins and bin width can be configured by the network operator, or can have a predetermined value. From two histograms, the distribution of abnormal release call duration and normal release call duration can be clearly shown. In addition, it is also possible to show the calculated mean value CD1 of the normal release call duration on each histogram, the calculated mean value CD2 of the abnormal release call duration or other relevant parameters or KPI.

[0059] In addition to its mean value, it is also possible to determine other statistics of the normal call duration or abnormal call duration, such as a standard deviation value, a probability distribution function, etc. The standard deviation values ​​of normal release calls and abnormal release calls can be represented by δ1 and δ2, respectively. Therefore, (CD1-δ1, CD1+δ1) can represent an interval, and a sample of normal release calls will fall into this interval with a probability of about 70% of the normal distribution function; and (CD2-δ2, CD2+δ2) can represent an interval, and a sample of abnormal release calls will fall into this interval with a probability of about 70% of the normal distribution function. In addition, if the number of each bin is divided by the sum of the numbers of all bins, it can provide the probability that a sample of call duration will fall into this bin, and then the probability distribution function can be obtained.

[0060] In addition, it should also be noted that there may be some very special cases when there is a group of calls with very short duration in the observed cell, so that the observed cell has a very low probability of abnormal release. Therefore, these durations of normal release calls can be filtered. Usually, such a group of calls will have another peak and a fairly short duration. In view of this, these calls should be distinguished based on the presence of two peaks in the histogram of normal call durations, and the group of calls with the lower peak can be excluded from consideration, as follows Figure 3B as shown in .

[0061] Figure 4An example method for network performance monitoring according to some other embodiments of the present disclosure is illustrated. Method 400 may be performed at a management function, such as an EMS / NMS or a third-party tool, such as a network management tool (e.g., NetAct Compact commercially available from Nokia Corporation) or a network analysis tool (e.g., Traffica commercially available from Nokia Corporation). In the following, the management function (particularly the EMS / NMS) will be described for illustrative purposes only, without imposing any limitation on the scope of the present disclosure.

[0062] like Figure 4 As shown in, in block 410, the average value of the duration of the normal released calls and the average value of the duration of the abnormal released calls monitored in the measurement period are received. As mentioned below, the base station determines the average value and sends the determined average value to, for example, a management function. At the management function, it can receive the average value for further processing.

[0063] In block 420, a relative difference between the normal call duration and the abnormal call duration is determined based on the received average value. In particular, the relative difference between the normal release call duration and the abnormal release call duration may be determined as a ratio between the relative difference between the average value of the duration of the normal release call and the average value of the duration of the abnormal release call and the average value of the duration of the normal release call. For example, the relative difference may be represented by σ and determined as

[0064] σ(%)=100*(CD1-CD2) / CD1 (1)

[0065] Wherein CD1 indicates the average duration of normal released calls, and CD2 indicates the average duration of abnormal released calls.

[0066] The relative difference σ between normal call duration and abnormal call duration can be used as a new maintainability KPI for network performance, which may help operators to optimize network performance. For example, cells whose network performance needs to be optimized may be determined based on the determined relative difference σ.

[0067] In particular, based on the relative difference and the threshold, the cells can be divided into: a group including cells that urgently need to perform network performance optimization to improve the QCI1 E-RAB drop rate KPI, and another group including cells that are less urgent or do not need network performance optimization. The cells belonging to the group that is less urgent or does not need network performance optimization can be those cells with a lower value of the relative difference index σ, for example, in the range of tens or hundreds (%). The cells belonging to the group that urgently needs to perform network performance optimization can be those cells with a larger value of the relative difference index σ, for example, in the range of tens (%). The threshold or range for classifying cells is provided only for illustrative purposes, and in fact, it can be configured or determined by the respective operators.

[0068] From the end user's perspective, a relative difference σ in the lower value range can indicate that almost the entire call is completed (compared to the expected call duration). On the contrary, a relative difference σ in the higher value range may mean that only a small or negligible part is completed (compared to the expected call duration). Therefore, for the latter case, the cell should attract the attention of the operator to perform some network performance optimizations, regardless of the QCI1 E-RAB drop rate KPI value reported for the observed cell. Therefore, by using the relative difference as a new maintainability KPI, scenarios can be easily identified, which would normally be overlooked when the scenario is only monitored based on the QCI1E-RAB drop rate KPI.

[0069] In some embodiments of the present disclosure, the management function or third-party tool may also receive the distribution of normal release call durations and the distribution of abnormal release call durations, and display the distribution of normal release call durations and the distribution of abnormal release call durations.

[0070] In some embodiments of the present disclosure, the distribution of normal release call duration and abnormal release call duration can be obtained by Figure 3A The two histograms shown in are represented. In particular, the first histogram can be used for normal release call duration, and has a plurality of bins corresponding to a plurality of call duration time intervals, each of the bins having a height indicating the number of normal release calls within the corresponding call duration time interval. The second histogram is used for abnormal release call duration, and has a plurality of bins corresponding to a plurality of call duration time intervals, each of the bins having a height indicating the number of abnormal release calls within the corresponding call duration time interval.

[0071] In addition to its average value, other statistics of normal call duration or abnormal call duration, such as standard deviation value, probability distribution function, etc., can also be displayed. As mentioned above, the value range (CD1-δ1, CD1+δ1) can represent the interval, and the sample of normal release calls will fall into this interval with a probability of about 70% of the normal distribution function; while the value range (CD1-δ1, CD1+δ1) can represent the interval, and the sample of abnormal release calls will fall into this interval with a probability of about 70% of the normal distribution function. In addition, it can provide such a probability that the sample of call duration will fall into this bin, and then the probability distribution function can be obtained.

[0072] In some other embodiments of the present disclosure, it is also possible to construct a three-dimensional model representing a key performance indicator of maintainability of network performance based on the first histogram and the second histogram.

[0073] Figure 5 A schematic diagram of an example 3D KPI model according to some example embodiments of the present disclosure is illustrated, the model having KPI cones for normal release call duration and abnormal release call duration. As shown, in the 3D model, there are two cones 510, 520, each having a central cylinder and at least one outer cylinder, which are constructed based on two histograms. Compared with the indicator of the relative difference σ between normal call duration and abnormal call duration, the cone of KPI can provide a more complex and enhanced view. This is because statistics (including not only mean values, but also standard deviation values, probability distribution functions, etc.) can be reflected from the two cones. In other words, all these indicators can be observed in the two cones for normal release call duration and abnormal release call duration.

[0074] In particular, the degree of overlap of the two KPI cones can also provide an additional visual KPI indicator for network performance. In other words, the cones of the KPI provide an observation of the intersection of the 3D histogram function, where the operator can complexly monitor how far the dropped calls from the active call duration are from the normal released calls. For example, two histograms with essentially the same probability distribution can indicate that there is no need for emergency optimization of the observed cell. On the other hand, two histograms without any intersection area can indicate that the dropped calls of the active call duration are far from the normal released calls, and therefore network performance optimization is required. Therefore, with the two KPI cones, it can also identify such a scenario that may not be discovered when using the "relative difference between normal call duration and abnormal call duration", especially in the case of low standard deviation values.

[0075] Furthermore, although Figure 5It is not depicted in the diagram, but it should be noted that some other indicators may also be provided by some 3D tools, such as the percentage of overlap of two histograms. In fact, the specific information displayed on the cone of the KPI can be determined based on actual needs and may therefore vary from operator to operator.

[0076] Figure 6 FIG. 4 illustrates a flowchart of constructing a KPI cone for abnormal release call duration according to some example embodiments of the present disclosure. Figure 6 As shown in , in block 610, a starting point is determined in the xy domain, the starting point being determined to have an x-coordinate and a y-coordinate, which correspond to the average value (CD2) of the duration of the monitored abnormal release calls. Then, in block 620, a central cylinder is constructed, and the central cylinder may have a height and a diameter, with the starting point as the center point of the central cylinder, corresponding to the height and width of the middle bin of the histogram for the duration of the abnormal release calls, respectively.

[0077] As used herein, the middle bin refers to a bin of the histogram for abnormal release call durations, into which the average value (CD2) of the monitoring durations of abnormal release calls falls. The average value (CD2) of the monitoring durations of abnormal release calls may fall into only one bin, and in this case, the height and diameter of the central cylinder may be determined, for example, as values ​​corresponding to the height and width of the middle bin, respectively. There may also be a case where the average value (CD2) of the monitoring durations of abnormal release calls happens to be located in Figure 7 . In this case, the two bins may be considered as intermediate bins. The central cylinder may have a diameter corresponding to the sum of the two intermediate bins, and the cylinder may have a height in the first half corresponding to the height of the right bin of the two intermediate bins, and may have a height in the second half corresponding to the height of the left bin of the two intermediate bins.

[0078] In block 630, at least one outer cylinder is constructed. The at least one outer cylinder corresponds to the at least two symmetrical outer bins around the middle bin. For the abnormal release call duration, the at least one outer bin may have a height corresponding to the height of the two symmetrical outer bins and a diameter corresponding to the sum of the widths of the two symmetrical outer bins and the bin therebetween.

[0079] For example, for the first outer cylinder, it has in the first half a height corresponding to the height of the first bin to the right of the middle bin, and in the second half a height corresponding to the height of the first bin to the left of the middle bin, and a diameter corresponding to the sum of the widths of the two bins and the middle bin. Figure 7As shown in , for the second outer cylinder, the height of the first half portion thereof can be determined as the height corresponding to the height of the second bin on the left side of the middle bin, and the height of the second half portion thereof can be determined as the height corresponding to the second bin on the right side of the middle bin. Its diameter can be determined as the sum of the widths of the second bin on the left side of the middle bin, the second bin on the right side of the middle bin, and the bins therebetween (including the first bin on the left side of the middle bin, the middle bin, and the first bin on the right side of the middle bin).

[0080] Similar operations can be repeated for other symmetrical bins around the middle bin (third right and left bins of the middle bin, fourth right and left bins of the middle bin, etc.). As a result, it is possible to obtain a cone 510 for abnormal release calls, having a central cylinder and at least one outer cone, such as Figure 6 as shown in .

[0081] Figure 8 Also illustrated is a flow chart for constructing a KPI cone for normal release call duration according to some example embodiments of the present disclosure. Figure 8 As shown in , in block 810, a starting point is determined in the xy domain, and the starting point has an x ​​coordinate and a y coordinate, both of which correspond to the average value (CD1) of the monitoring duration of the normal release call. Then, in block 820, a central cylinder is constructed, the central cylinder having a height and a diameter, with the starting point as the center point of the central cylinder, corresponding to the height and width of the middle bin of the histogram for the normal release call duration, respectively.

[0082] Similarly, the middle bin refers to a bin of the histogram for the duration of normal release calls, into which the average value (CD1) of the monitoring duration of normal release calls falls. In the case where the average value (CD1) of the monitoring duration of normal release calls is exactly between two bins in the histogram, the two bins can be regarded as middle bins. In this case, the diameter of the central cylinder can be determined as the sum of the two middle bins, and the cylinder can have a height corresponding to the height of the right bin of the two middle bins in the first half, and can have a height corresponding to the height of the left bin of the two middle bins in the second half.

[0083] In block 830, at least one outer cylinder is constructed. For normal release call duration, the at least one outer cylinder has a height corresponding to the height of the two symmetrical outer bins and a diameter corresponding to the sum of the widths of the two symmetrical outer bins and the bin between them in the histogram. The operation of constructing at least one outer cylinder is similar to the operation described in block 630, with the only difference being that the construction of the cylinder is based on the histogram for normal release call duration, rather than the histogram for abnormal release call duration.

[0084] As described above, the degree of overlap of the two cones indicates the urgency of network performance optimization. For example, if the two cones have a large overlap, this indicates that there is less urgency or no urgency in the observed cell for network performance optimization, and if there is no intersection area between them, this means that the dropped calls from the active call duration are far from the normal release calls, so the cell has an urgent need for network performance. Therefore, through the two cones, it is possible to provide a visual indication of network performance.

[0085] Fig. 9 FIG. 1 illustrates a signaling flow chart of an example method for monitoring network performance according to some example embodiments of the present disclosure. Fig. 9 As shown in, in step 901, in response to a call request from an end user, the eNB can send an initial context setup message to an evolved packet center (EPC). In step 902, the EPC establishes a UE context and sends an initial context setup response to the eNB. Then, in step 903, the E-RAB duration value is reset, and in step 904, when the E-RAB is active, the eNB calculates the E-RAB duration. In step 905, the eNB sends a UE context release request, which may be caused by normal release or abnormal release (such as dropped calls). In step 906, the EPC releases the UE context and sends back a UE context release response. Afterwards, in step 907, if the E-RAB is released normally, the eNB generates a normal release call duration (d1), and triggers the corresponding histogram bin counter of the normal release call. On the other hand, if the E-RAB is released abnormally, in step 908, the eNB generates an abnormal release call duration (d2), and triggers the corresponding histogram bin counter of the abnormal release call. The operations from step 901 to step 908 may be repeated until the measurement period ends.

[0086] After the measurement period ends, in step 909, the eNB may calculate the average normal release call duration (CD2) and the abnormal release call duration (CD1), respectively. In step 910, the eNB may report the monitoring results to the EMS / NMS, including the histogram and the calculated average value for the normal release call duration and the abnormal release call duration. In step 911, the EMS / NMS may calculate the relative difference, display the histogram and construct the KPI cone, as described above.

[0087] Fig.10 A flowchart of an example implementation for network performance monitoring according to some example embodiments of the present disclosure is illustrated. The method may be executed at a base station.

[0088] First, at the beginning of a new measurement period, all counters and variables are reset to zero. As shown in the figure, in box 1001, in response to a call request from a terminal user, a voice call is established through a call establishment procedure. For the E-UTRAN system, the voice call can be implemented by QCI 1E-RAB, and it can be established by sending an initial context setup response or an E-RAB setup response message from the eNB to the mobility management entity (MME). For the NR system, the voice call can be implemented by the QF1Qos process, and it can be established by sending an initial context response or a QF11 QOS process setup response from the gNB to the access management function (AMF).

[0089] In box 1002, the base station stores the time point at which the voice call has been established. Further, in box 1003, it is determined whether the voice call has been released according to the 3GPP specification. For example, for the E-UTRAN system, the 3GPP specification can be 3GPP TS36.413; for the NR system, the 3GPP specification can be, for example, 3GPP TS 37.340. In each specification, it provides a distinction between each normal and abnormal call release. Therefore, it can identify a normal release call and an abnormal release call. If the call is not released according to the specification, it can be identified as a scenario, which can also check whether it should be excluded from monitoring.

[0090] Therefore, if it is affirmative in box 1003, the method enters box 1004 and the base station stores the time point as T1, then in step 1009, the call duration is calculated as T1 to T0, and in step 1010, based on 3GPP, the corresponding histogram bin counter for abnormal release calls or normal release calls is triggered according to the distinction result. In step 1011, the base station also determines the total duration of the normal release call.

[0091] If the answer is negative in box 1003, in step 1005, the base station also determines where the RLF or inactivity timer has been started, and if the answer is also negative, the method returns to box 1003; if the answer is positive, the method enters box 1006, and the base station stores the time point as T1.

[0092] Further, in block 1007, the base station may also determine whether the voice call has been released according to the 3GPP specification. If it is negative in block 1007, in block 1012, it is further determined whether the RLF or inactivity timer has stopped. If it has stopped, the base station removes T1 of the call, and the method returns to block 1003; if it has not stopped, the method returns to block 1007. On the other hand, if it is positive in block 1007, the method enters block 1008, and if it has not stopped, the time point is stored as T1 of the call, and the method continues to execute blocks 1009 to 1011 to record the monitoring values ​​of the normal release call or the abnormal release call.

[0093] After block 1011, in block 1014, it is further determined whether the measurement period has expired. If so, the base station can calculate the average values ​​of the normal release call duration and the abnormal release call duration, respectively, and report the monitoring results, including the histogram and the average values, to the management function. If not, in block 1015, the base station further determines whether another voice call has been established. If another voice call has been established, the method enters block 1002 to monitor the other call; if another voice call has not been established, the method enters block 1014 to check whether the measurement period has expired.

[0094] It should be noted that Fig. 9 and Fig.10 It is given for the purpose of illustration only and does not impose any limitation on the scope of the present disclosure. There may be some modifications, additions, deletions, changes, etc., which are also covered by the present disclosure.

[0095] Fig.11 is a simplified block diagram of a device 1100 suitable for implementing an example embodiment of the present disclosure. The device 110 may be implemented at or as part of a management function or a base station.

[0096] As shown, the device 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a communication module 1130 coupled to the processor 1110, and a communication interface (not shown) coupled to the communication module 1130. The memory 1120 stores at least a program 1140. The communication module 1130 is used for two-way communication, for example, through multiple antennas. The communication interface can represent any interface necessary for communication.

[0097] Assume that program 1140 includes program instructions that, when executed by associated processor 1110, enable device 1100 to operate in accordance with example embodiments of the present disclosure, as referred to herein. Figures 2 to 10The example embodiments herein may be implemented by computer software (executed by the processor 1110 of the device 1100), or by hardware, or by a combination of software and hardware. The processor 1110 may be configured to implement various example embodiments of the present disclosure, such as any of the methods 200, 400, 600, 800, 900, and 1000.

[0098] The memory 1120 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology, such as non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory, as non-limiting examples. Although only one memory 1120 is shown in the device 1100, there may be several physically different memory modules in the device 1100. The processor 1110 may be of any type suitable for the local technology network and may include one or more of the following as non-limiting examples: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 1100 may have multiple processors, such as a dedicated integrated circuit chip, which is time-slave to a clock that synchronizes the main processor.

[0099] When the device 1100 acts as a base station 110 or a portion thereof, the processor 1110 and the communication module 1130 may cooperate to implement the above reference Figure 2 , Fig. 9 and Fig.10 The method 200, part of the method 900 and the method 100 described above. When the device 1100 acts as a management function 130 or a third-party tool or part thereof, the processor 1110 and the communication module 1130 can cooperate to implement the above Figure 4 , Figure 6 , Figure 8 and Fig. 9 Portions of method 400, method 600, method 800, and method 900 are described.

[0100] Refer to above Figures 2 to 10 All operations and features described are equally applicable to the device 1100 and have the same effects. For the sake of simplicity, the details will be omitted.

[0101] In general, various example embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the example embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representations, it is to be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0102] The present disclosure also provides at least one computer program product, which is tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as instructions included in program modules, which are executed in a device on a target real or virtual processor to perform the above-referenced Figure 2 , Figure 4 , Figure 6 , Figure 8 , Fig. 9 and Fig.10 Methods 200, 400, 600, 800, 900 and 1000 are described. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc., which perform tasks or implement specific abstract data types. In various example embodiments, the functionality of program modules can be combined or divided between program modules as needed. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0103] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, implements the functions / operations specified in the flow chart and / or block diagram. The program code can be executed entirely on the machine, partially on the machine, as an independent software packet, partially on the machine and partially on a remote computer or entirely on a remote machine or server.

[0104] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier wave, so that a device, apparatus or processor can perform the above-mentioned various processes and operations. Examples of carrier waves include signals, computer-readable media, etc.

[0105] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or apparatuses or any suitable combination of the foregoing. More specific examples of computer readable storage media may include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), an optical storage device, a magnetic storage device or any suitable combination of the foregoing.

[0106] In order to implement the solution provided herein in the E_UTRAN system, some new measurements may be defined in the 3GPP standard and some new content may be added. In the following, new example measurements will be provided below for illustration purposes only.

[0107] For 3GPP TS 32.425, for example, the following four new measurements may be defined:

[0108] Distribution of normal release call (QCI1 E-RAB) duration

[0109] • This measurement provides a histogram result of the samples collected during the measurement period duration related to the duration of a normal release call (QCI1 E-RAB).

[0110] Cumulative counter (CC)

[0111] Due to normal release, each sample is measured from the point in time that the QCI1 E-RAB has been successfully established by initial context setup or additional E-RAB setup procedures according to 3GPP TS 36.413 until the point in time that the E-RAB is released by a release procedure initiated by the eNB or EPC. Periods with ongoing RLF or user inactivity timers are excluded from the measurement of sample duration.

[0112] Each measurement is an integer value.

[0113] • Measurement names are of the form QCI1ERAB.NormCallDurationBinX, where X represents the Xth bin out of a total of N configured bins.

[0114] ·Community

[0115] Valid for packet switching services

[0116] Evolved Packet System (EPS)

[0117] • Each histogram function is represented by an operator-configured number of bins with a configured bin width.

[0118] Distribution of abnormal release call (QCI1 E-RAB) duration

[0119] • This measurement provides a histogram result of the samples collected during the measurement period duration related to the duration of abnormal release calls (QCI1 E-RAB).

[0120] Cumulative counter (CC)

[0121] Due to abnormal release reasons, each sample is measured from the point in time when the QCI1 E-RAB has been successfully established through the initial context setup or additional E-RAB setup procedures according to 3GPP TS 36.413 until the point in time when the E-RAB is released through a release procedure initiated by the eNB or EPC. The period with ongoing RLF or user inactivity timer is excluded from the measurement of sample duration.

[0122] Each measurement is an integer value.

[0123] • Measurement names are of the form QCI1ERAB.AbnormCallDurationBinX, where X represents the Xth bin out of a total of N configured bins.

[0124] ·Community

[0125] ·Effective for packet switching services

[0126] EPS

[0127] • Each histogram function is represented by an operator-configured number of bins with a configured bin width.

[0128] Average normal release call (QCI1 E-RAB) duration

[0129] • This measurement provides the average value of the duration of a normal release call (QCI1 E-RAB).

[0130] Cumulative counter (CC)

[0131] At the end of the measurement period, the measurement is taken as the arithmetic mean of the samples of the normal release of the call (QCI1 E-RAB). Due to the normal release, each sample is measured from the time point when the QCI1 E-RAB has been successfully established by the initial context setup or additional E-RAB setup procedure according to 3GPP TS 36.413 until the time point when the E-RAB is released by the release procedure initiated by the eNB or EPC. The period with ongoing RLF or user inactivity timer is excluded from the measurement of the sample duration.

[0132] Each measurement is an integer value (in milliseconds).

[0133] The measurement name has the form QCI1ERAB.MeanNormCallDuration.

[0134] ·Community

[0135] Valid for packet switching services

[0136] EPS

[0137] Mean abnormal release call (QCI1 E-RAB) duration

[0138] • This measurement provides the average value of the abnormal release call (QCI1 E-RAB) duration.

[0139] Cumulative counter (CC)

[0140] At the end of the measurement period, the measurement is taken as the arithmetic mean of the samples of abnormal release calls (QCI1 E-RAB). Due to abnormal release, each sample is measured from the time point when the QCI1 E-RAB has been successfully established by initial context setup or additional E-RAB setup procedure according to 3GPP TS 36.413 until the time point when the E-RAB is released by a release procedure initiated by the eNB or EPC. The period with ongoing RLF or user inactivity timer is excluded from the measurement of sample duration.

[0141] Each measurement is an integer value (in milliseconds).

[0142] The measurement name has the form QCI1ERAB.MeanAbnormCallDuration.

[0143] ·Community

[0144] Valid for packet switching services

[0145] Evolved Packet System (EPS)

[0146] Alternatively, use case A2 in this specification can be modified by adding underscores as follows:

[0147] E-RAB releases "A2 monitoring

[0148] E-RAB is a critical and limited resource used by E-UTRAN to deliver services. The release of E-RAB needs to be monitored as follows:

[0149] - Abnormal release of E-RAB will cause call ( / session) drop, which will directly affect the QoS delivered by the network and the satisfaction of end users;

[0150] - A successfully released E-RAB can be used to set up other requested calls ( / sessions). An E-RAB that cannot be released still occupies limited resources, so it cannot be used to acknowledge other requested calls ( / sessions).

[0151] From the retainability measurement aspect, the E-RABs do not need to be released since they are inactive, they can be retained to give fast access when new data arrives.

[0152] In order to define (from the point of view of E-RAB release measurements) whether an E-RAB is considered active or not, E-RABs can be divided into two groups:

[0153] a. Continuous processes are always considered to be active E-RABs, i.e. independent of whether there is ongoing traffic at the time. Examples: VoIP sessions, real-time sessions, live streaming sessions.

[0154] b. Burst flow, an E-RAB is considered active only when there is data in the UL / DL buffer.

[0155] Example: Web Session.

[0156] How to decide whether an E-RAB is a burst-type flow or a continuous-type flow for a particular QCI is outside the scope of this document.

[0157] The specific reasons for abnormal and failed release of E-RAB are needed to find the problem and determine the solution. In addition, due to the different priorities and tolerances of different service types with different QoS levels in the network, a monitor needs to be turned on for each service type with QoS level.

[0158] The E-RAB can be released through the following procedures: E-RAB release procedure (see 3GPP TS 36.413 [9]), UE context release procedure (see 3GPP TS 36.413 [9] and 3GPP TS 36.423

[10] ), reset procedure initiated by eNodeB or MM (see 3GPP TS 36.413 [9]), path switch procedure (see 3GPP TS 36.413 [9]) and eNB internal HO procedure (see 3GPP TS 36.331 [8]).

[0159] Therefore, performance measurements related to the E-RAB release (see 3GPP TS 36.413 [9]) and UE context release (see 3GPP TS 36.413 [9]) procedures for each service type with QoS level are necessary to support the monitoring of E-RAB release.

[0160] It should be noted that from a quality perspective, the expected call duration for the same value is much lower than the expected call duration if the call is not dropped. E-RAB loss or UE context loss can be perceived by the end user in different ways, especially for The duration of the call is 90% for VoIP traffic. In both cells, there is a 90% E-RAB drop rate, but in the first cell there is Dropped calls, however, lasted 99% of the expected call duration compared to dropped calls, where the expected call 40% of the duration will certainly be perceived by the end user in different ways. In the first case, the end user has a high The probability will not follow the additional call request, and in the second cell, the terminal user has a high probability of placing the second call to Same called party.

[0161] Therefore, as an extended monitoring, especially for VoIP sessions, it is recommended to observe the "Normal Release Call (QCI1E-RAB) The distribution of durations" and "Distribution of durations of normal release calls (QCI1E-RAB)" and the corresponding average values ​​of normal and abnormal release call (QCI1E-RAB) duration measurements. ”

[0162] A corresponding part may also be added in section 5.2.1.2 in 3GPP TS 32.451.

[0163] "5.2.1.2 Specification level requirements

[0164] The maintainability of end-user applications covers an area wider than just the E-UTRAN part. Therefore, it is important to realise that the KPIs for this in E-UTRAN should be limited to the part that E-UTRAN already controls, i.e. the E-UTRAN KPIs should be defined so that they indicate the contribution of E-UTRAN to the end-user impact, rather than trying to take responsibility for the entire end-to-end part of service maintainability.

[0165] The service provided by E-UTRAN for this KPI shall be E-RAB.

[0166] Due to the possibility of E-RAB keepalive, that is, DRX is available, the keepalive time of E-RAB is likely to be much longer than the time they are used to transmit data. With this extreme setting of keepalive functionality, it can lead to that basically all E-RAB releases are destined to be abnormal (if keepalive is set very long, normal system release does not exist).

[0167] Therefore, the definition is that it is considered an abnormal release only when there is a real impact on the end user.

[0168] The preferred normalization of exception releases of services should be the time unit transferred between exception releases, ie, exception releases per service session time.

[0169] KPIs should be available for each QoS group.

[0170] It should be noted that from a quality perspective, the two different The same value of E-RAB drop ratio in a cell can be perceived by end users in different ways, especially for The duration of dropped calls for VoIP services. There is a 90% E-RAB drop rate in both cells, but in the first cell There are dropped calls, but the duration of the dropped calls is 99% of the expected call duration, where the expected 40% of the call duration will certainly be perceived by the end user in different ways. In the first case, the end user has There is a high probability that the additional call request will not be followed, and in the second cell, the terminal user has a high probability of placing the second call Dial to the same called party.

[0171] Therefore, the definition of VoIP service is,by observing the "distribution of the duration of normal release calls (QCI1E-RAB)" and "Distribution of normal release call (QCI1E-RAB) duration" and mean normal and abnormal release call duration The measurement not only focuses on abnormal release, but also on the difference between normal release call duration and abnormal release call duration. difference.

[0172] A corresponding part may also be added in section 6.2.1.2 in 3GPP TS 32.450.

[0173] 6.2.1.2 Extended Definition

[0174] a) The maintainability ratio is defined as:

[0175] Number of abnormally released E-RABs with data in any buffer / active E-RAB time [Releases / Session time]

[0176] Regarding the definition of abnormal E-RAB release with end-user impact, only when the eNodeB believes that there is data waiting to be transmitted in any buffer, it should be considered as an abnormal release of the E-RAB.

[0177] With regard to defining an E-RAB as active, an E-RAB shall be considered active if there has currently been any data transmission in either direction.

[0178] b) "The relative difference between normal call duration and abnormal call duration" is defined as:

[0179]

[0180] Among them, QCI1ERAB.MeanNormCallDuration, QCI1ERAB.MeanAbnormCallDuration, llDuration 3GPP TS 32.425 or defined by the cone of KPIs, which is defined as 3D view of the QCI1ERAB.NormCallDuration bin X and QCI1ERAB.AbnormCallDuration bin X histograms. ”

[0181] For example, a 3D view can be Figure 5 The 3D KPI model shown in .

[0182] For NR systems, some new measurements also need to be defined to implement the solution provided in this article. In the following, new example measurements will be provided below for illustration purposes only.

[0183] For example, new measurements may be defined in 3GPP TS 28.522 as follows:

[0184] Distribution of duration of normal call release (QFI1 QoS process)

[0185] • This measurement provides a histogram result of samples collected during the measurement period duration related to the duration of a normal release call (QFI1 QoS flow).

[0186] Cumulative counter (CC)

[0187] Due to normal release, each sample is measured from the point in time when the QFI1 QoS flow has been successfully established via the Initial Context Setup or Additional QFI1 QoS flow setup procedure as per 3GPP TS 37.340 until the point in time when the QFI1 QoS flow is released via a Release procedure initiated by the nhNB or AMF. The period with ongoing RLF or User Inactivity Timer is excluded from the measurement of sample duration.

[0188] Each measurement is an integer value.

[0189] • Measurement names are of the form QFI1.Rel.NormCallDurationBinX, where X represents the Xth bin out of a total of N configured bins.

[0190] ·Community

[0191] Valid for packet switching services

[0192] 5GS

[0193] • Each histogram function is represented by an operator-configured number of bins with a configured bin width.

[0194] Distribution of abnormal release call (QFI1 QoS process) duration

[0195] • This measurement provides a histogram result of samples collected during the measurement period duration related to the duration of abnormal released calls (QFI1 QoS flow).

[0196] Cumulative counter (CC)

[0197] Due to abnormal release reasons, each sample is measured from the time point when the QFI1 QoS flow has been successfully established through the Initial Context Setup or Additional QFI1 QoS flow setup procedures as per 3GPP TS 37.340 until the time point when the QFI1 QoS flow is released through a Release procedure initiated by the nhNB or AMF. The time period with ongoing RLF or User Inactivity Timer is excluded from the measurement of sample duration.

[0198] Each measurement is an integer value.

[0199] • Measurement names are of the form QFI1.Rel.AbnormCallDurationBinX, where X represents the Xth bin out of a total of N configured bins.

[0200] ·Community

[0201] Valid for packet switching services

[0202] 5GS

[0203] • Each histogram function is represented by an operator-configured number of bins with a configured bin width.

[0204] Average normal release call (QFI1 QoS process) duration

[0205] • This measurement provides the average value of the duration of a normal release call (QFI1 QoS flow).

[0206] Cumulative counter (CC)

[0207] At the end of the measurement period, the measurement is taken as the arithmetic mean of the samples of the normal release of the call (QFI1 QoS procedure). Due to the normal release, each sample is measured from the time point when the QCI1 E-RAB has been successfully established by the initial context setup or additional QFI1 QoS procedure setup procedure according to 3GPP TS 37.340 until the time point when the QFI1 QoS procedure is released by the release procedure initiated by the nhNB or AMF. The time period with ongoing RLF or user inactivity timer is excluded from the measurement of the sample duration.

[0208] Each measurement is an integer value (in milliseconds).

[0209] The measurement name has the form QFI1.Rel.MeanNormCallDuration.

[0210] ·Community

[0211] Valid for packet switching services

[0212] 5GS

[0213] Average abnormal release call (QFI1 QoS process) duration

[0214] • This measurement provides the average value of abnormal release call (QFI1 QoS flow) duration.

[0215] Cumulative counter (CC)

[0216] At the end of the measurement period, the measurement is taken as the arithmetic mean of the samples of abnormally released calls (QFI1 QoS procedures). Each sample is measured from the time point when the QFI1 QoS procedure has been successfully established by the Initial Context Setup or the Additional E-RAB Setup procedure according to 3GPP TS 37.340 until the time point when the QFI1 QoS procedure is released by the Release procedure initiated by the nhNB or AMF, due to the abnormal release. The time period with ongoing RLF or the User Inactivity Timer is excluded from the measurement of the sample duration.

[0217] Each measurement is an integer value (in milliseconds).

[0218] The measurement name has the form QFI1.Rel.MeanAbnormCallDuration.

[0219] ·Community

[0220] Valid for packet switching services

[0221] 5GS

[0222] It should be noted that the above measurement definitions and additions are only provided for illustrative purposes and do not impose any limitation on the scope of the present disclosure. For any of them, there may be some modifications, deletions, changes and additions, all of which are covered by the present disclosure.

[0223] Further, although the operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order, or requiring all of the operations shown to be performed to achieve the desired result. In some cases, multitasking and parallel processing can be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be viewed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to a particular example embodiment. Certain features described in the context of a separate example embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple example embodiments individually or in any suitable sub-combination.

[0224] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0225] Various example embodiments of the technology have been described. In addition to or as an alternative to the above examples, the following examples are described. Features described in any of the following examples can be used with any other examples described herein.

[0226] In some aspects, a method is provided. The method includes: monitoring durations of normal release calls and durations of abnormal release calls during a measurement period; determining an average value of the monitored durations of normal release calls and an average value of the monitored durations of abnormal release calls based on the monitored durations of normal release calls and the monitored durations of abnormal release calls; and sending the average value of the monitored durations of normal release calls and the monitored durations of abnormal release calls.

[0227] In some example embodiments, each of the durations of the normally released calls is measured from a point in time when the call is successfully established until the call is normally released, and each of the durations of the abnormally released calls is measured from a point in time when the call is successfully established until the call is abnormally released.

[0228] In some example embodiments, at least one of a radio link failure time period and an inactivity time period of an observed end user is excluded from monitoring.

[0229] In some example embodiments, the method further includes: determining the distribution of normal released call durations and the distribution of abnormal released call durations in multiple call duration time intervals accordingly based on the monitoring duration of normal released calls and the monitoring duration of abnormal released calls within a measurement period; and sending the distribution of normal released call durations and the distribution of abnormal released call durations.

[0230] In some example embodiments, the distribution of normal released call duration is represented by a first histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of normally released calls within the corresponding call duration time interval; and the distribution of abnormal released call duration is represented by a second histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of abnormally released calls within the corresponding call duration time interval.

[0231] In some example embodiments, the method further comprises filtering durations of a group of normal release calls, the durations of the group of normal release calls having a duration peak value that is much lower than duration peak values ​​of other normal release calls.

[0232] In some aspects, a method is provided. The method includes: receiving an average value of durations of normal released calls and an average value of durations of abnormal released calls monitored during a measurement period; and determining a relative difference between the durations of normal released calls and the durations of abnormal released calls based on the average value of durations of normal released calls and the average value of durations of abnormal released calls.

[0233] In some example embodiments, determining the relative difference further comprises determining the relative difference between the duration of the normal released calls and the duration of the abnormal released calls as a ratio between the relative difference between the average value of the duration of the normal released calls and the average value of the duration of the abnormal released calls and the average value of the duration of the normal released calls.

[0234] In some example embodiments, the method further comprises determining a cell in which network performance needs to be optimized based on the determined relative difference.

[0235] In some example embodiments, the method further includes receiving a distribution of normal released call durations and a distribution of abnormal released call durations; and displaying the distribution of the normal released call durations and the distribution of the abnormal released call durations.

[0236] In some example embodiments, the distribution of normal released call duration is represented by a first histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of normally released calls within the corresponding call duration time interval; and the distribution of abnormal released call duration is represented by a second histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of abnormally released calls within the corresponding call duration time interval.

[0237] In some example embodiments, the method further comprises constructing a three-dimensional model representing a maintainability key performance indicator of network performance based on the first histogram and the second histogram.

[0238] In some example embodiments, constructing a three-dimensional model representing a maintainability key performance indicator of network performance further comprises: constructing a first cone in an xy domain, having a central cylinder and at least one outer cylinder having a central point with coordinate values, both corresponding to average values ​​of the monitoring duration of the normally released calls, wherein the central cylinder has a height and a diameter, respectively corresponding to the height and width of a middle bin in the first histogram, into which the average value of the monitoring duration of the normally released calls falls, and the at least one outer cylinder has a height corresponding to the height of two symmetrical outer bins and a diameter corresponding to the sum of the widths of the two symmetrical outer bins and the bin therebetween in the first histogram; and constructing a second cone in the xy domain, having another central cylinder and at least another outer cylinder with a center point having coordinates, both corresponding to the average values ​​of the monitoring duration of abnormal release calls, the other central cylinder having a height and a diameter corresponding respectively to the height and width of a middle bin in the second histogram, into which the average value of the monitoring duration of abnormal release calls falls, and at least another outer cylinder having a height corresponding to the height of two symmetrical outer bins and a diameter corresponding to the sum of the widths of two symmetrical outer bins and the bin between them in the second histogram, wherein the degree of overlap between the first cone and the second cone visually indicates the urgency of network performance optimization.

[0239] In some aspects, a device is provided. The device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to cause the device, through the at least one processor, to: monitor the duration of normal release calls and the duration of abnormal release calls during a measurement period; determine an average value of the duration of the monitored normal release calls and the average value of the duration of the monitored abnormal release calls based on the monitored duration of the normal release calls and the monitored duration of the abnormal release calls; and send the average value of the monitored duration of the normal release calls and the average value of the monitored duration of the abnormal release calls.

[0240] In some example embodiments, each duration of a normally released call is measured from a time point when the call is successfully established until the call is normally released, and each duration of an abnormally released call is measured from a time point when the call is successfully established until the call is abnormally released.

[0241] In some example embodiments, at least one of a radio link failure time period and an inactivity time period of an observed end user is excluded from monitoring.

[0242] In some example embodiments, the device is also configured to: determine the distribution of normal released call durations and the distribution of abnormal released call durations in multiple call duration time intervals based on the monitoring duration of normal released calls and the monitoring duration of abnormal released calls within a measurement period; and send the distribution of normal released call durations and the distribution of abnormal released call durations.

[0243] In some example embodiments, the distribution of normal released call duration is represented by a first histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of normally released calls within the corresponding call duration time interval; and the distribution of abnormal released call duration is represented by a second histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of abnormally released calls within the corresponding call duration time interval.

[0244] In some example embodiments, the device is further caused to filter a group of durations of normal release calls whose duration peaks are much lower than duration peaks of other normal release calls.

[0245] In some aspects, a device is provided. The device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to cause the device, through the at least one processor, to: receive an average value of durations of normal released calls and an average value of durations of abnormal released calls monitored during a measurement period; and determine a relative difference between the durations of normal released calls and the durations of abnormal released calls based on the average value of durations of normal released calls and the average value of durations of abnormal released calls.

[0246] In some example embodiments, determining the relative difference further comprises determining the relative difference between the duration of the normal released calls and the duration of the abnormal released calls as a ratio between the relative difference between the average value of the duration of the normal released calls and the average value of the duration of the abnormal released calls and the average value of the duration of the normal released calls.

[0247] In some example embodiments, the apparatus is further caused to determine a cell for which network performance needs to be optimized based on the determined relative difference.

[0248] In some example embodiments, the device is further caused to: receive a distribution of normal released call durations and a distribution of abnormal released call durations; and display the distribution of normal released call durations and the distribution of abnormal released call durations.

[0249] In some example embodiments, the distribution of normal released call duration is represented by a first histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of normally released calls within the corresponding call duration time interval; the distribution of abnormal released call duration is represented by a second histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of abnormally released calls within the corresponding call duration time interval.

[0250] In some example embodiments, the apparatus is further caused to construct a three-dimensional model representing a maintainability key performance indicator of network performance based on the first histogram and the second histogram.

[0251] In some example embodiments, constructing a three-dimensional model representing a maintainability key performance indicator of network performance includes: constructing a first cone in an xy domain, having a central cylinder and at least one outer cylinder having a central point with coordinate values, both corresponding to average values ​​of monitoring durations of normally released calls, wherein the central cylinder has a height and a diameter corresponding to the height and width of a middle bin in a first histogram, respectively, into which the average value of monitoring durations of normally released calls falls, and the at least one outer cylinder has a height corresponding to the height of two symmetrical outer bins and a diameter corresponding to the sum of the widths of the two symmetrical outer bins and a bin therebetween in the first histogram; and constructing a second cone in the xy domain, having another central cylinder and at least another outer cylinder with a center point having coordinates, both corresponding to the average values ​​of the monitoring duration of abnormal release calls, the other central cylinder having a height and a diameter corresponding respectively to the height and width of a middle bin in the second histogram, into which the average value of the monitoring duration of abnormal release calls falls, and at least another outer cylinder having a height corresponding to the height of two symmetrical outer bins and a diameter corresponding to the sum of the widths of two symmetrical outer bins and the bin between them in the second histogram, wherein the degree of overlap between the first cone and the second cone visually indicates the urgency of network performance optimization.

[0252] In some aspects, an apparatus is provided. The apparatus includes: a component for monitoring durations of normal release calls and durations of abnormal release calls during a measurement period; a component for determining average values ​​of monitoring durations of normal release calls and average values ​​of monitoring durations of abnormal release calls based on the monitoring durations of normal release calls and monitoring durations of abnormal release calls; and a component for sending the average values ​​of monitoring durations of normal release calls and average values ​​of monitoring durations of abnormal release calls.

[0253] In some example embodiments, each duration of the durations of the normally released calls is measured from a point in time when the call is successfully established until the call is released normally, and each duration of the abnormally released calls is measured from a point in time when the call is successfully established until the call is released abnormally.

[0254] In some example embodiments, at least one of a radio link failure time period and an inactivity time period of an observed end user is excluded from monitoring.

[0255] In some example embodiments, the apparatus further comprises: a component for determining, based on the monitoring duration of the normal released calls and the monitoring duration of the abnormal released calls within a measurement period, the distribution of the normal released call durations and the distribution of the abnormal released call durations in a plurality of call duration time intervals, respectively; and a component for transmitting the distribution of the normal released call durations and the distribution of the abnormal released call durations.

[0256] In some example embodiments, the distribution of normal released call duration is represented by a first histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of normally released calls within the corresponding call duration time interval; and the distribution of abnormal released call duration is represented by a second histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of abnormally released calls within the corresponding call duration time interval.

[0257] In some example embodiments, the apparatus further comprises means for filtering durations of a group of normal release calls, the durations of the group of normal release calls having a duration peak value much lower than duration peak values ​​of other normal release calls.

[0258] In some aspects, an apparatus is provided. The apparatus includes: a component for receiving an average value of durations of normal released calls and an average value of durations of abnormal released calls monitored during a measurement period; and a component for determining a relative difference between a normal released call duration and an abnormal released call duration based on the average value of durations of normal released calls and the average value of durations of abnormal released calls.

[0259] In some example embodiments, the component for determining the relative difference is further configured to determine the relative difference between the normal release call duration and the abnormal release call duration as: the ratio between the relative difference between the average value of the duration of the normal release calls and the average value of the duration of the abnormal release calls and the average value of the duration of the normal release calls.

[0260] In some example embodiments, the apparatus further comprises means for determining a cell for which network performance needs to be optimized based on the determined relative difference.

[0261] In some example embodiments, the apparatus further comprises: means for receiving a distribution of normal released call durations and a distribution of abnormal released call durations; and means for displaying the distribution of normal released call durations and the distribution of abnormal released call durations.

[0262] In some example embodiments, the distribution of normal released call duration is represented by a first histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of normally released calls within the corresponding call duration time interval; the distribution of abnormal released call duration is represented by a second histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each bin having a height indicating the number of abnormally released calls within the corresponding call duration time interval.

[0263] In some example embodiments, the method further includes means for constructing a three-dimensional model representing a maintainability key performance indicator of network performance based on the first histogram and the second histogram.

[0264] In some example embodiments, the component for constructing a three-dimensional model representing a maintainability key performance indicator of network performance is further configured to: construct a first cone in an xy domain, having a central cylinder and at least one outer cylinder having a central point with coordinate values, both corresponding to average values ​​of the monitoring duration of the normally released calls, wherein the central cylinder has a height and a diameter, respectively corresponding to a height and a width of a middle bin in the first histogram, into which the average value of the monitoring duration of the normally released calls falls, and the at least one outer cylinder has a height corresponding to the height of two symmetrical outer bins and a diameter corresponding to two symmetrical outer bins in the first histogram. The invention relates to a method for optimizing the network performance of a network. The method comprises the steps of: constructing a second cone in the xy domain, having another central cylinder and at least another outer cylinder with a center point having coordinates, both corresponding to the average values ​​of the monitoring duration of abnormal release calls, the other central cylinder having a height and a diameter, respectively corresponding to the height and width of the middle bin in the second histogram, into which the average value of the monitoring duration of abnormal release calls falls, and at least another outer cylinder having a height corresponding to the height of the two symmetrical outer bins and a diameter corresponding to the sum of the widths of the two symmetrical outer bins and the bins between them in the second histogram. The degree of overlap between the first cone and the second cone visually indicates the urgency of network performance optimization.

Claims

1. A method of communication, comprising: monitoring the duration of the normal release calls and the duration of the abnormal release calls during the measurement period; Based on the monitored duration of the normal released calls and the monitored duration of the abnormal released calls, correspondingly determining an average value of the monitored duration of the normal released calls and an average value of the monitored duration of the abnormal released calls; as well as sending the average value of the monitored duration of the normal released calls and the average value of the monitored duration of the abnormal released calls, wherein the average value of the duration of the monitored normal released calls and the average value of the duration of the monitored abnormal released calls are used to determine the relative difference between the duration of the normal released calls and the duration of the abnormal released calls, and The relative difference is used to determine cells that need to be optimized for network performance.

2. The method according to claim 1, wherein each of the durations of the normal release call is measured from a time point when a call is successfully established until the call is normally released, and Each of the durations of the abnormally released calls is measured from a time point when a call is successfully established until the call is abnormally released. 3 . The method of claim 1 , wherein at least one of a radio link failure time period and an inactivity time period for the observed end user is excluded from the monitoring.

4. The method according to claim 1, further comprising: Based on the monitored durations of the normal released calls and the monitored durations of the abnormal released calls during a measurement period, a distribution of normal released call durations and a distribution of abnormal released call durations in a plurality of call duration time intervals are determined accordingly; and The distribution of normal released call durations and the distribution of abnormal released call durations are transmitted.

5. The method of claim 4, wherein the distribution of normal release call durations is represented by a first histogram having a plurality of bins corresponding to the plurality of call duration time intervals, each of the bins having a height indicating: the number of the normal release calls within the corresponding call duration time interval; and The distribution of abnormal release call duration is represented by a second histogram having a plurality of bins corresponding to the plurality of call duration time intervals, each of the bins having a height indicating the number of the abnormal release calls within the corresponding call duration time interval.

6. The method according to claim 4, further comprising: A duration of a group of normal release calls is filtered, the duration of the group of normal release calls having a duration peak value much lower than a duration peak value of other normal release calls.

7. A method of communication, comprising: receiving an average value of durations of normal released calls and an average value of durations of abnormal released calls monitored during a measurement period; determining a relative difference between the duration of the normal released calls and the duration of the abnormal released calls based on the average value of the duration of the normal released calls and the average value of the duration of the abnormal released calls; as well as A cell that needs to be optimized for network performance is determined based on the determined relative difference.

8. The method of claim 7, wherein determining the relative difference further comprises: The relative difference between the normal release call duration and the abnormal release call duration is determined as a ratio between a difference between the average value of the durations of normal release calls and the average value of the durations of abnormal release calls and the average value of the durations of normal release calls.

9. The method according to claim 7, further comprising: Receive the distribution of normal release call durations and the distribution of abnormal release call durations.

10. The method of claim 9, wherein the distribution of normal release call durations is represented by a first histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each of the bins having a height indicating: the number of the normal release calls within the corresponding call duration time interval; and The distribution of abnormal release call duration is represented by a second histogram having a plurality of bins corresponding to the plurality of call duration time intervals, each of the bins having a height indicating the number of the abnormal release calls within the corresponding call duration time interval.

11. The method according to claim 10, further comprising: Based on the first histogram and the second histogram, a three-dimensional model representing a key performance indicator of maintainability of network performance is constructed.

12. The method according to claim 11, wherein constructing a three-dimensional model representing a key performance indicator of maintainability of the network performance further comprises: constructing a first cone in an xy domain, the first cone having a central cylinder and at least one outer cylinder having a central point with coordinate values, the central cylinder and the at least one outer cylinder corresponding to the average value of the monitoring duration of normal release calls, wherein the central cylinder has a height and a diameter, the height and the diameter respectively corresponding to the height and the width of a middle bin in the first histogram, the average value of the monitoring duration of normal release calls falling into the middle bin, and the at least one outer cylinder has a height corresponding to the height of two symmetrical outer bins and a diameter corresponding to the sum of the widths of the two symmetrical outer bins and the bin therebetween in the first histogram; and constructing a second cone in the xy domain, the second cone having another central cylinder and at least another outer cylinder with a central point having coordinates, the another central cylinder and the at least another outer cylinder corresponding to the average value of the monitoring duration of abnormal release calls, the another central cylinder having a height and a diameter, the height and the diameter corresponding to the height and the width of a middle bin in the second histogram, respectively, the average value of the monitoring duration of abnormal release calls falling in the middle bin, and the at least another outer cylinder having a height corresponding to the height of two symmetrical outer bins and a diameter corresponding to the sum of the widths of the two symmetrical outer bins and the bins therebetween in the second histogram, The extent to which the first cone and the second cone are overlapped visually indicates the urgency of network performance optimization.

13. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: monitoring the duration of the normal release calls and the duration of the abnormal release calls during the measurement period; as well as Based on the monitored duration of the normal released calls and the monitored duration of the abnormal released calls, correspondingly determining an average value of the monitored duration of the normal released calls and an average value of the monitored duration of the abnormal released calls; sending the average value of the monitored duration of the normal released calls and the average value of the monitored duration of the abnormal released calls, wherein the average value of the duration of the monitored normal released calls and the average value of the duration of the monitored abnormal released calls are used to determine the relative difference between the duration of the normal released calls and the duration of the abnormal released calls, and The relative difference is used to determine cells that need to be optimized for network performance.

14. The apparatus according to claim 13, wherein each of the durations of the durations of the normal release calls is measured from a time point when a call is successfully established until the call is normally released, and Each of the durations of the abnormally released calls is measured from a time point when a call is successfully established until the call is abnormally released.

15. The apparatus of claim 13, wherein at least one of a radio link failure time period and an inactivity time period for the observed end user is excluded from the monitoring.

16. The apparatus of claim 13, wherein the apparatus is further caused to: Based on the monitored durations of the normal released calls and the monitored durations of the abnormal released calls during a measurement period, a distribution of normal released call durations and a distribution of abnormal released call durations in a plurality of call duration time intervals are determined accordingly; and The distribution of normal released call durations and the distribution of abnormal released call durations are transmitted.

17. The apparatus of claim 16, wherein the distribution of normal release call durations is represented by a first histogram having a plurality of bins corresponding to the plurality of call duration time intervals, each of the bins having a height indicating: the number of the normal release calls within the corresponding call duration time interval; and The distribution of abnormal release call duration is represented by a second histogram having a plurality of bins corresponding to the plurality of call duration time intervals, each of the bins having a height indicating the number of the abnormal release calls within the corresponding call duration time interval.

18. The apparatus of claim 17, wherein the apparatus is further caused to: A duration of a group of normal release calls is filtered, the duration of the group of normal release calls having a duration peak value much lower than a duration peak value of other normal release calls.

19. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: receiving an average value of durations of normal released calls and an average value of durations of abnormal released calls monitored during a measurement period; determining a relative difference between the duration of the normal released calls and the duration of the abnormal released calls based on the average value of the duration of the normal released calls and the average value of the duration of the abnormal released calls; as well as A cell that needs to be optimized for network performance is determined based on the determined relative difference.

20. The apparatus of claim 19, wherein determining the relative difference further comprises: The relative difference between the normal release call duration and the abnormal release call duration is determined as a ratio between a difference between the average value of the durations of normal release calls and the average value of the durations of abnormal release calls and the average value of the durations of normal release calls.

21. The apparatus of claim 19, wherein the apparatus is further caused to: Receive the distribution of normal release call durations and the distribution of abnormal release call durations.

22. The apparatus of claim 21, wherein the distribution of normal release call durations is represented by a first histogram having a plurality of bins corresponding to a plurality of call duration time intervals, each of the bins having a height indicating: the number of the normal release calls within the corresponding call duration time interval; and The distribution of abnormal release call duration is represented by a second histogram having a plurality of bins corresponding to the plurality of call duration time intervals, each of the bins having a height indicating the number of the abnormal release calls within the corresponding call duration time interval.

23. The apparatus of claim 22, wherein the apparatus is further caused to: Based on the first histogram and the second histogram, a three-dimensional model representing a key performance indicator of maintainability of network performance is constructed.

24. The apparatus according to claim 23, wherein said constructing a three-dimensional model representing a key performance indicator of maintainability of said network performance further comprises: constructing a first cone in an xy domain, the first cone having a central cylinder and at least one outer cylinder having a central point with coordinate values, the central cylinder and the at least one outer cylinder corresponding to the average value of the monitoring duration of normal release calls, wherein the central cylinder has a height and a diameter, the height and the diameter respectively corresponding to the height and the width of a middle bin in the first histogram, the average value of the monitoring duration of normal release calls falling into the middle bin, and the at least one outer cylinder has a height corresponding to the height of two symmetrical outer bins and a diameter corresponding to the sum of the widths of the two symmetrical outer bins and the bin therebetween in the first histogram; and constructing a second cone in the xy domain, the second cone having another central cylinder and at least another outer cylinder with a central point having coordinates, the another central cylinder and the at least another outer cylinder corresponding to the average value of the monitoring duration of abnormal release calls, the another central cylinder having a height and a diameter, the height and the diameter corresponding to the height and the width of a middle bin in the second histogram, respectively, in which the average value of the monitoring duration of abnormal release calls falls, and the at least another outer cylinder having a height corresponding to the height of two symmetrical outer bins and a diameter corresponding to the sum of the widths of the two symmetrical outer bins and the bin between them in the second histogram, The extent to which the first cone and the second cone are overlapped visually indicates the urgency of network performance optimization.

25. An apparatus for communication, comprising: means for monitoring the duration of normal release calls and the duration of abnormal release calls during a measurement period; for determining an average value of the monitored duration of the normal released calls and an average value of the monitored duration of the abnormal released calls based on the monitored duration of the normal released calls and the monitored duration of the abnormal released calls; as well as means for transmitting the average value of the monitored duration of the normal released calls and the average value of the monitored duration of the abnormal released calls, wherein the average value of the duration of the monitored normal released calls and the average value of the duration of the monitored abnormal released calls are used to determine the relative difference between the duration of the normal released calls and the duration of the abnormal released calls, and The relative difference is used to determine cells that need to be optimized for network performance.

26. An apparatus for communication, comprising: means for receiving an average value of durations of normal released calls and an average value of durations of abnormal released calls monitored during a measurement period; means for determining a relative difference between a normal release call duration and an abnormal release call duration based on said average value of the durations of the normal release calls and said average value of the durations of the abnormal release calls; as well as A cell that needs to be optimized for network performance is determined based on the determined relative difference.

27. A computer-readable storage medium comprising program instructions stored thereon, which instructions, when executed by a processor of a device, cause the device to perform the method according to any one of claims 1 to 6.

28. A computer-readable storage medium comprising program instructions stored thereon, which instructions, when executed by a processor of a device, cause the device to perform the method according to any one of claims 7 to 12.

Images