Project

General

Profile

Feature #1655

KPIs for OsmoSGSN

Added by laforge about 2 years ago. Updated 6 months ago.

Status:
Stalled
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/11/2016
Due date:
% Done:

80%

Spec Reference:

Description

  • overall GPRS DL and UL IP payload throughput (mbps) : waits for compression
  • overall GPRS DL and UL IP compression gain (%) : waits for compression
  • overall GPRS DL and UL LLC througput (mbps) : via global rate counters
  • GPRS Attach attempts (number) : gprs.attempts_request
  • GPRS Attach success rate (%) : gprs.attempts_accepted / gprs.attempts_request
  • PDP context attempts (number) : pdp.activate_requests
  • PDP context establish success rate (%) : pdp.activate_requests / pdp.activate_accept
  • PDP context cut-off (%) : ?

Related issues

Related to Cellular Network Infrastructure - Bug #1652: Expose statistics / KPIs programmatically New 03/11/2016
Related to OsmoSGSN - Bug #1581: IP payload compression Closed 02/23/2016
Related to OsmoSGSN - Feature #1580: IP header compression Closed 02/23/2016

History

#1 Updated by laforge about 2 years ago

  • Related to Bug #1652: Expose statistics / KPIs programmatically added

#2 Updated by laforge almost 2 years ago

  • Assignee set to lynxis

#3 Updated by lynxis almost 2 years ago

known statistics of a fresh unconnected sgsn

OsmoSGSN> show asciidoc 
// generating tables for rate_ctr_group
// rate_ctr_group table NSVC Peer Statistics
.ns.nsvc - NSVC Peer Statistics 
|===
| name | This document & | description
| packets.in | <<ns.nsvc_packets.in>> | Packets at NS Level  ( In)
| packets.out | <<ns.nsvc_packets.out>> | Packets at NS Level  (Out)
| bytes.in | <<ns.nsvc_bytes.in>> | Bytes at NS Level    ( In)
| bytes.out | <<ns.nsvc_bytes.out>> | Bytes at NS Level    (Out)
| blocked | <<ns.nsvc_blocked>> | NS-VC Block count         
| dead | <<ns.nsvc_dead>> | NS-VC gone dead count     
| replaced | <<ns.nsvc_replaced>> | NS-VC replaced other count
| nsei-chg | <<ns.nsvc_nsei-chg>> | NS-VC changed NSEI count  
| inv-nsvci | <<ns.nsvc_inv-nsvci>> | NS-VCI was invalid count  
| inv-nsei | <<ns.nsvc_inv-nsei>> | NSEI was invalid count    
| lost.alive | <<ns.nsvc_lost.alive>> | ALIVE ACK missing count   
| lost.reset | <<ns.nsvc_lost.reset>> | RESET ACK missing count   
|===
// generating tables for osmo_stat_items
NSVC Peer Statistics
// osmo_stat_item_group table NSVC Peer Statistics
.ns.nsvc - NSVC Peer Statistics 
|===
| name | This document & | description | unit
| alive.delay | <<ns.nsvc_alive.delay>> | ALIVE reponse time         | ms
|===
// generating tables for osmo_counters
// ungrouped osmo_counters
.ungrouped osmo counters
|===
| name | This document & | description
|===

#4 Updated by lynxis almost 2 years ago

PDP context cut-off (%) means

PDP Cut Off Ratio = 100%* (Total Undesired PDP Deactivation/Total active PDP)

Total Undesired PDP Deactivation:
Success_undesired_Deactivation / Deactivation_Success_ratio*

* deactivation Success Ratio:
IU_SUCC_NWR_PDP_CON_DEACT/(IU_SUCC_NWR_PDP_CON_DEACT+
IU_FAIL_NWR_PDP_CON_DEACT)

Success_undesired_Deactivation:
IU_NWR_PDP_DEACT_38+ IU_NWR_PDP_DEACT_39+ IU_NWR_PDP_DEACT_OTH

Total Active PDP:
(PEAK_ACTIVE_IU_PDP_CONTEXTS+ MIN_ACTIVE_IU_PDP_CONTEXTS)/2 +
IU_SUCC_MO_PDP_CON_ACT+ IU_MO_SEC_PDP_ACTIVATION_SUCC

source: http://www.finetopix.com/showthread.php/22324-3G-PDP-Cut-Off-Degradation

#5 Updated by lynxis almost 2 years ago

overall GPRS DL and UL IP compression gain (%)

no compression support
will be 0

#6 Updated by lynxis almost 2 years ago

  • Status changed from New to In Progress

#7 Updated by lynxis almost 2 years ago

  • Related to Bug #1581: IP payload compression added

#8 Updated by lynxis almost 2 years ago

#9 Updated by lynxis almost 2 years ago

counter are now implemented for

    CTR_LLC_DL_PACKETS, /* done */
    CTR_LLC_UL_PACKETS, /* done */
    CTR_LLC_DL_BYTES, /* done */
    CTR_LLC_UL_BYTES, /* done */
    CTR_LLC_DL_IP_PAYLOAD_BYTES, /* unused waiting for compression support */
    CTR_LLC_UL_IP_PAYLOAD_BYTES, /* unused waiting for compression support */
    CTR_GPRS_ATTACH_REQUEST, /* added */
    CTR_GPRS_ATTACH_ACKED, /* added */
    CTR_GPRS_ATTACH_REJECTED, /* added */
    CTR_GPRS_DETACH_REQUEST, /* added */
    CTR_GPRS_DETACH_ACKED, /* added */
    CTR_GPRS_ROUTING_AREA_REQUEST, /* added */
    CTR_GPRS_ROUTING_AREA_ACKED,  /* added */
    CTR_GPRS_ROUTING_AREA_REJECT, /* added */
    /* PDP single packet counter / GSM 04.08 9.5.1 - 9.5.9 */
    CTR_PDP_ACTIVATE_REQUEST, /* done */
    CTR_PDP_ACTIVATE_REJECT, /* done */
    CTR_PDP_ACTIVATE_ACCEPT, /* done */
    CTR_PDP_REQUEST_ACTIVATE, /* unused network -> ms */
    CTR_PDP_REQUEST_ACTIVATE_REJ, /* unsued ms -> network */
    CTR_PDP_MODIFY_REQUEST, /* unsued */
    CTR_PDP_MODIFY_ACCEPT, /* unused */
    CTR_PDP_DEACTIVATE_REQUEST, /* done */
    CTR_PDP_DEACTIVATE_ACCEPT, /* done */

next step is putting the counters into seperate commits and test those.

#10 Updated by lynxis almost 2 years ago

  • Description updated (diff)

#11 Updated by lynxis almost 2 years ago

  • % Done changed from 0 to 80

cut is still missing

#12 Updated by lynxis almost 2 years ago

  • Description updated (diff)

#13 Updated by lynxis over 1 year ago

cut-off is a ratio of: (activated pdp context failed) / (pdp context activated)

#14 Updated by laforge over 1 year ago

what is the status?

#15 Updated by laforge 8 months ago

  • Priority changed from Normal to Urgent

#16 Updated by lynxis 7 months ago

  • Status changed from In Progress to Stalled

overall GPRS DL and UL IP payload throughput (mbps) : waits for compression
- missing, wasn't implemented after compression support written
overall GPRS DL and UL IP compression gain (%) : waits for compression
- missing, wasn't implemented after compression support written

overall GPRS DL and UL LLC througput (mbps) : via global rate counters
- implemented { "llc.dl_bytes", "Count sent LLC bytes before giving it to the bssgp layer" }, { "llc.dl_packets", "Count sucessful sent LLC packets before giving it to the bssgp layer" }, { "llc.ul_bytes", "Count sucessful received LLC bytes (encrypt & fcs correct)" }, { "llc.ul_packets", "Count sucessful received LLC packets (encrypt & fcs correct)" },

GPRS Attach attempts (number) : gprs.attempts_request
- implemented { "gprs.attach_requested", "Received attach requests" },

GPRS Attach success rate (%) : gprs.attempts_accepted / gprs.attempts_request
- implemented { "gprs.attach_accepted", "Sent attach accepts" }, { "gprs.attach_rejected", "Sent attach rejects" },

PDP context attempts (number) : pdp.activate_requests
- implemented { "pdp.activate_requested", "Received activate requests" },

PDP context establish success rate (%) : pdp.activate_requests / pdp.activate_accept
- implemented: { "pdp.activate_rejected", "Sent activate rejects" }, { "pdp.activate_accepted", "Sent activate accepts" },

PDP context cut-off (%) : ?
- missing
How should we find out "undesired" pdp context deact?

#17 Updated by laforge 6 months ago

  • Priority changed from Urgent to Normal

Also available in: Atom PDF