Pcs Reference Guide

RedKnee PCS v8.0_0.1ADoc Version 1.1

Reference Guide

A-P1310-A-01 Approval Date 01 Sep 2014

2

Reference Guide

Intellectual Property

Copyright 1999-2014 Redknee Inc. All rights reserved.

The following documentation, the content therein and/or the presentation of its

information is proprietary to and embodies the confidential processes, designs,

technologies and otherwise of Redknee Inc. All copyright, trademarks, trade names,

patents, industrial designs, and other intellectual property rights contained herein are,

unless otherwise specified, the exclusive property of Redknee Inc.

The ideas, concepts and/or their application, embodied within this documentation remain

and constitute items of intellectual property which nevertheless belong to Redknee Inc.

The information (including, but by no means limited to, data, drawings, specifications,

documentation, software listings, source and/or object code) shall not be disclosed,

manipulated, disseminated or otherwise in any manner inconsistent with the nature and/

or conditions under which this documentation has been issued.

The information contained herein is believed to be accurate and reliable. Except as

otherwise provided, Redknee Inc. accepts no responsibility for its use in any way

whatsoever. Except as otherwise provided, Redknee Inc. shall not be liable for any

expenses, damages and/or related costs which may result from the use of any information

contained hereafter.

Except as otherwise provided, the information contained herein is subject to change

without notice. The copyright herein is expressly protected at common law, statute and

under various International and Multi-National Treatises (including, but by no means

limited to, the Berne Convention for the Protection of Literary and Artistic Works).

Reference Guide

Table of Contents

1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 Change history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Configuration Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 CPCS architecture and supported interfaces. . . . . . . . . . . . . . . . . . . . . 112.2.1 Peer network policy table parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2.2 Gq-or-Rx-Interface and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.3 Gx-Interface and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.2.4 SPR-Search-Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.2.5 Sh-Interface and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.2.6 LDAP-Interface and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.2.6.1 LDAP parameters in basic configuration file . . . . . . . . . . . . . . . . . . . . . 342.2.7 Common parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.2.8 SPR Interface and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.2.9 Smpp-Interface and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.2.10 Plugin-Interface and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.2.11 SOAP-Interface and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412.2.12 Generic-Notification-Interface and parameters . . . . . . . . . . . . . . . . . . . 422.2.13 Core general configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . 432.2.14 Attribute parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.2.15 Service configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.2.16 Subscriber parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.2.17 QoS Selection parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652.3 Restrictions for PCM objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3 Counter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.1.1 Types of counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.1.2 Types of PCS Performance Counters . . . . . . . . . . . . . . . . . . . . . . . . . . 713.1.3 Viewing counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.1.4 Guideline to check counter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.2 Key performance indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.2.1 Administering key performance indicators . . . . . . . . . . . . . . . . . . . . . . . 723.2.2 Creating KPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.2.3 Examples of KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.2.3.1 Valid Gq messages received rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.2.3.2 Invalid Gq messages received rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.2.3.3 Valid Ia messages received rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.2.3.4 Invalid Ia messages received rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.2.3.5 Rate of messages denied by the Policy Rule Engine . . . . . . . . . . . . . . 773.2.3.6 Rate of messages permitted by the Policy Rule Engine . . . . . . . . . . . . 783.2.3.7 Ratio of rejected Gq messages due to overload . . . . . . . . . . . . . . . . . . 79

3

Reference Guide

3.3 Internal counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.4 Performance counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.4.1 Common counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.4.1.1 Group contexts currently existing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.4.1.2 Gq /Rx terminals max in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.4.1.3 terminals currently existing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.4.1.4 terminals ever created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.4.1.5 terminals max in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.4.1.6 Subscribers currently existing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.4.1.7 Subscribers ever created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.4.1.8 Subscribers created in last period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.4.1.9 messages permitted by Policy Rule Engine for ever . . . . . . . . . . . . . . . 833.4.1.10 messages permitted by Policy Rule Engine in last period . . . . . . . . . . . 833.4.1.11 messages denied by Policy Rule Engine for ever. . . . . . . . . . . . . . . . . . 843.4.1.12 messages denied by Policy Rule Engine in last period . . . . . . . . . . . . . 843.4.2 Gq interface counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.4.2.1 valid Gq messages ever received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.4.2.2 valid Gq messages received in last period . . . . . . . . . . . . . . . . . . . . . . . 843.4.2.3 invalid Gq messages ever received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.4.2.4 invalid Gq messages received in last period. . . . . . . . . . . . . . . . . . . . . . 853.4.2.5 Gq messages ever sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.4.2.6 Gq messages sent in last period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.4.2.7 rejecting Non Overload Gq messages ever sent . . . . . . . . . . . . . . . . . . 853.4.2.8 rejecting Non Overload Gq messages sent in last period. . . . . . . . . . . . 863.4.2.9 rejecting overload Gq messages ever sent. . . . . . . . . . . . . . . . . . . . . . . 863.4.2.10 rejecting overload Gq messages sent in last period . . . . . . . . . . . . . . . . 863.4.3 Rx interface counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.4.3.1 valid Rx messages ever received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.4.3.2 valid Rx messages received in last period . . . . . . . . . . . . . . . . . . . . . . . 873.4.3.3 invalid Rx messages ever received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.4.3.4 invalid Rx messages received in last period . . . . . . . . . . . . . . . . . . . . . . 873.4.3.5 Rx messages ever sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.4.3.6 Rx messages sent in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.4.3.7 rejecting Non Overload Rx messages ever sent. . . . . . . . . . . . . . . . . . . 883.4.3.8 rejecting Non Overload Rx messages sent in last period . . . . . . . . . . . . 883.4.3.9 rejecting overload Rx messages ever sent . . . . . . . . . . . . . . . . . . . . . . . 883.4.3.10 rejecting overload Rx messages sent in last period . . . . . . . . . . . . . . . . 893.4.3.11 rejecting overload Rx messages which are ever dropped . . . . . . . . . . . 893.4.3.12 rejecting overload Rx messages dropped in last period . . . . . . . . . . . . . 893.4.3.13 Rx sessions currently existing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.4.3.14 Rx sessions ever created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.4.3.15 Rx sessions created in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.4.3.16 Rx sessions ever released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.4.3.17 Number of hanging Rx contexts deleted by PCS . . . . . . . . . . . . . . . . . . 903.4.3.18 Rx Emergency sessions created in last period . . . . . . . . . . . . . . . . . . . . 913.4.3.19 Rx Emergency sessions currently existing . . . . . . . . . . . . . . . . . . . . . . . 913.4.3.20 Rx emergency sessions dropped in last period . . . . . . . . . . . . . . . . . . . 91

4

Reference Guide

3.4.3.21 Rx emergency sessions ever created. . . . . . . . . . . . . . . . . . . . . . . . . . 913.4.3.22 Rx Emergency sessions ever dropped . . . . . . . . . . . . . . . . . . . . . . . . . 913.4.3.23 RX Priority Sessions Currently Existing . . . . . . . . . . . . . . . . . . . . . . . . . 923.4.3.24 RX Priority Sessions Dropped in Last Period . . . . . . . . . . . . . . . . . . . . 923.4.3.25 RX Priority Sessions ever dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.4.3.26 RX Priority Sessions Created in Last Period . . . . . . . . . . . . . . . . . . . . . 923.4.3.27 RX Priority Sessions Ever Created . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.4.4 Gx interface counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.4.4.1 valid Gx messages ever received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.4.4.2 valid Gx messages received in last period. . . . . . . . . . . . . . . . . . . . . . . 933.4.4.3 invalid Gx messages ever received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.4.4.4 invalid Gx messages received in last period . . . . . . . . . . . . . . . . . . . . . 943.4.4.5 Number of hanging Gx contexts deleted by PCS . . . . . . . . . . . . . . . . . 943.4.4.6 Gx messages ever sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943.4.4.7 Gx messages sent in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.4.4.8 rejecting Non overload Gx messages ever sent . . . . . . . . . . . . . . . . . . 953.4.4.9 rejecting Non overload Gx messages sent in last period. . . . . . . . . . . . 953.4.4.10 rejecting overload Gx messages ever sent . . . . . . . . . . . . . . . . . . . . . . 953.4.4.11 rejecting overload Gx messages sent in last period . . . . . . . . . . . . . . . 963.4.4.12 PDP activations for ever . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.4.4.13 PDP activations in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.4.4.14 Number of successful CCA-I sent for ever. . . . . . . . . . . . . . . . . . . . . . . 963.4.4.15 Number of successful CCA-I sent in last period . . . . . . . . . . . . . . . . . . 963.4.4.16 Number of CCR-U received for ever . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.4.4.17 Number of CCR-U received in last period . . . . . . . . . . . . . . . . . . . . . . . 973.4.4.18 Number of successful CCA-U sent for ever . . . . . . . . . . . . . . . . . . . . . . 973.4.4.19 Number of successful CCA-U sent in last period. . . . . . . . . . . . . . . . . . 973.4.4.20 Number of successful RAA received for ever . . . . . . . . . . . . . . . . . . . . 983.4.4.21 Number of successful RAA received in last period . . . . . . . . . . . . . . . . 983.4.4.22 Number of unsuccessful RAA received for ever . . . . . . . . . . . . . . . . . . 983.4.4.23 Number of unsuccessful RAA received in last period . . . . . . . . . . . . . . 983.4.4.24 Number of RAA timed out for ever. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.4.4.25 Number of RAA timed out in last period. . . . . . . . . . . . . . . . . . . . . . . . . 993.4.4.26 Number of CCR-T received for ever . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.4.4.27 Number of CCR-T received in last period . . . . . . . . . . . . . . . . . . . . . . . 993.4.4.28 Number of successful CCA-T sent for ever . . . . . . . . . . . . . . . . . . . . . . 993.4.4.29 Number of successful CCA-T sent in last period . . . . . . . . . . . . . . . . . 1003.4.4.30 Number of GXRAR messages sent for ever . . . . . . . . . . . . . . . . . . . . 1003.4.4.31 Number of GXRAR messages sent in last period . . . . . . . . . . . . . . . . 1003.4.4.32 Gx Initial Message Rejected in last period. . . . . . . . . . . . . . . . . . . . . . 1003.4.4.33 Gx Initial Message Rejected Ever . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.4.4.34 usage limit exceeded in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.4.4.35 usage limit exceeded for ever . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.4.4.36 number of Gx messages dropped when load level is VERY_CRITICAL. .

1013.4.4.37 Gx sessions currently existing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.4.4.38 Gx sessions ever created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

5

Reference Guide

3.4.4.39 Gx sessions created in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.4.4.40 Gx bearers currently existing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.4.4.41 Gx bearers ever created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.4.4.42 Gx bearers created in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.4.4.43 Gx sessions ever released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033.4.4.44 Gx Emergency sessions created in last period. . . . . . . . . . . . . . . . . . . 1033.4.4.45 Gx Emergency sessions currently existing . . . . . . . . . . . . . . . . . . . . . . 1033.4.4.46 Gx emergency sessions dropped in last period . . . . . . . . . . . . . . . . . . 1033.4.4.47 Gx emergency sessions ever created. . . . . . . . . . . . . . . . . . . . . . . . . . 1043.4.4.48 Gx Emergency sessions ever dropped . . . . . . . . . . . . . . . . . . . . . . . . . 1043.4.4.49 Gx Priority Sessions Currently Existing . . . . . . . . . . . . . . . . . . . . . . . . 1043.4.4.50 Gx Priority Session SPR based created in Last period. . . . . . . . . . . . . 1043.4.4.51 Gx Priority Session SPR based ever created . . . . . . . . . . . . . . . . . . . . 1043.4.4.52 Gx Priority Session SPR based dropped in Last Period . . . . . . . . . . . . 1053.4.4.53 Gx Priority Sesions SPR based Ever Dropped . . . . . . . . . . . . . . . . . . . 1053.4.4.54 Gx Priority Sessions Rx Session Based Created in last Period . . . . . . 1053.4.4.55 Gx Priority Sessions RX Session Based ever created . . . . . . . . . . . . . 1053.4.4.56 Gx Priority Sessions RX session Based Dropped in Last Period . . . . . 1053.4.4.57 Gx Priority Sessions RX session Based Ever Dropped . . . . . . . . . . . . 1063.4.5 Ia interface counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.4.5.1 valid Ia messages ever received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.4.5.2 valid Ia messages received in last period . . . . . . . . . . . . . . . . . . . . . . . 1063.4.5.3 invalid Ia messages ever received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.4.5.4 invalid Ia messages received in last period . . . . . . . . . . . . . . . . . . . . . 1073.4.5.5 Ia messages ever sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.4.5.6 Ia messages sent in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.4.5.7 Ia messages ever dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.4.5.8 Ia messages dropped in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.4.6 Sh interface counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083.4.6.1 valid Sh messages ever received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083.4.6.2 valid Sh messages received in last period . . . . . . . . . . . . . . . . . . . . . . 1083.4.6.3 invalid Sh messages ever received . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083.4.6.4 invalid Sh messages received in last period . . . . . . . . . . . . . . . . . . . . . 1083.4.6.5 Sh messages ever sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093.4.6.6 Sh messages sent in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093.4.6.7 Sh messages Max sent per period . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093.4.7 LDAP interface counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093.4.7.1 invalid Ldap messages ever received. . . . . . . . . . . . . . . . . . . . . . . . . . 1093.4.7.2 invalid Ldap messages received in last period . . . . . . . . . . . . . . . . . . . 1103.4.7.3 valid Ldap messages ever received . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103.4.7.4 valid Ldap messages received in last period . . . . . . . . . . . . . . . . . . . . 1103.4.7.5 Ldap messages ever sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103.4.7.6 Ldap messages sent in last period . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103.4.8 SoapTrig interface counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1113.4.8.1 invalid subscriber trigger messages ever received . . . . . . . . . . . . . . . . 1113.4.8.2 invalid subscriber trigger received in last period . . . . . . . . . . . . . . . . . . 1113.4.8.3 valid subscriber trigger ever received . . . . . . . . . . . . . . . . . . . . . . . . . . 111

6

Reference Guide

3.4.8.4 valid subscriber trigger received in last period. . . . . . . . . . . . . . . . . . . 1113.4.8.5 Rejected Overload SOAP Messages Ever Sent . . . . . . . . . . . . . . . . . 1123.4.8.6 Rejected Overload SOAP Messages Sent in Last Period . . . . . . . . . . 1123.4.9 SMPP Notification interface counters . . . . . . . . . . . . . . . . . . . . . . . . . 1123.4.9.1 SMPP Messages Ever sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123.4.9.2 SMPP Messages Sent In Last Period . . . . . . . . . . . . . . . . . . . . . . . . . 1123.4.9.3 SMPP Messages Ever Received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.4.9.4 SMPP Messages Received In Last Period . . . . . . . . . . . . . . . . . . . . . 1133.4.10 GenericPlugin interface counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.4.10.1 Plugin Messages Ever Sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.4.10.2 Plugin Messages Ever Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.5 CAF Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143.5.1 Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143.5.1.1 Context operations on local farm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143.5.1.2 Context Replication toward remote farm . . . . . . . . . . . . . . . . . . . . . . . 1143.5.1.3 Context Replication status on remote farm . . . . . . . . . . . . . . . . . . . . . 116

4 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

7

Reference Guide

8

Reference Guide About this document

1 About this documentThis document provides information about PCS counters. It briefly describes all the counters, and also tells the user the importance of counters, where to check for coun-ters.

1.1 Intended audienceThis document addresses administrators/operators who are responsible for maintaining PCS.To get maximum benefit from this document, the user is expected to have knowledge of the following:

• Basic End-to-End call flows that involve PCS in IMS network. • In depth knowledge of all interfaces used in PCS like Gq, Ia, Gx, so on. • Telecommunication standards like ETSI TISPAN, 3GPP, and SMPP.USPR related parameters in Hostspecificconfigparams file and serviceconfig file are for future use only.APN-Name and APN-Override added in Host Specific Configuration table are for future use only.

1.2 Change historyNew software release: PCS 8.0_0.1A

1.3 Notational conventionsThis document uses the following notational conventions.

Version Date Section Description

1.0 26 Jun 2014 3.5 CAF Counters Added CAF counters related to Session Continuity feature.

28 Aug 2014 3.4.1 Common counters Added manual flush counters.

1.1 01 Sep 2014 2.2.6.1 LDAP parame-ters in basic configura-tion file

Updated LDAPRequestTimeout_s default value.

Table 1 Change history

Convention Indicates...

Bold Any field or text in the GUI

italic • File, folder, or directory names and file extensions (.pdf) • Values to be inserted in an empty field/box • Emphasized text

Courier System commands and screen outputs

Table 2 Notational conventions

9Id:0900d80580a318a40900d80580a3

18a4

Reference GuideAbout this document

“Quote” Window or wizard titles

Menu > Path Menu paths

Keyboard Buttons Keyboard buttons, for example, Enter

[Shortcut] Shortcuts, for example, [CTRL+ALT+DEL]

<angle brackets> Placeholders for concrete names or values

g Notes that provide additional information or helpful sugges-tions that apply to the subject text

Convention Indicates...

Table 2 Notational conventions (Cont.)

10 Id:0900d80580a318a40900d80580a318a4

Reference Guide Configuration Parameter

2 Configuration Parameter

2.1 IntroductionThe Configurable PCM GUI parameters chapter describes the PCM GUI parameters (Policy and Configuration Manager). It provides a description on the parameter. These parameters are accessible through the PCM GUI.Refer to the Operating PCS for further information on using the PCM Web GUI.

2.2 CPCS architecture and supported interfacesConverged PCS (CPCS) scenario provides both mobile and fixed network policy solu-tions. In CPCS scenario PCRF, DPI, are combined into one PCS solution. CPCS scenario supports various network nodes from different vendors. For configuration details refer Operating PCS.

g Internal-DB as SPR is not supported. Only Gx, Rx diameter interfaces are supported

Figure 1 shows CPCS architecture.

Figure 1 CPCS architecture

Following are the CPCS interfaces and parameters:1. Peer network policy table parameters2. Gq-or-Rx-Interface and parameters3. Gx-Interface and parameters4. SPR-Search-Info5. Sh-Interface and parameters6. LDAP-Interface and parameters7. Common parameters8. SPR Interface and parameters

11

Reference GuideConfiguration Parameter

9. Smpp-Interface and parameters10. Plugin-Interface and parameters11. SOAP-Interface and parameters12. Generic-Notification-Interface and parameters13. Core general configuration parameters14. Attribute parameters15. Service configuration parameters16. Subscriber parameters17. QoS Selection parameters

12


2.2.1 Peer network policy table parametersThis section includes all the peer networks connected to PCS.

S.No Parameter name

Description Type Value range Default

1 Peer-Network

This specifies details of each peer network.

Peer-Net-workType

NA NA

1.1.a Network-Name

It specifies the peer network name. string NA Nokia_IMS

1.1.b Domain-Name

It specifies the peer domain name. string NA www.nsn.com

1.2 List-Of-Binding Input-Range

It specifies the binding input address ranges of the peer network.

List-Of-BindingIn-put-Range-Type

NA NA

1.2.1 IP-Address-Prefix

Either an asterisk (*) or an IPv4 or IPv6 address prefix. Prefixes should not overlap throughout this file. The asterisk indicates any address (wildcard).

IPAddress-PrefixType

NA NA

1.2.1.a Address It represents an IP Address. IPv4 address is in a dotted decimal format and IPv6 address in textual format as described in RFC 3513Asterisk (*) can also be used. It functions as a wildcard that is any address is allowed. Example for IPv4: 130.12.2.0Example for IPv6: 12AB:0:0:CD30

IPAddress-Type

IPv4, IPv6 127.128.0.0

1.2.1.b Mask An integer from 1 to 32 indicating the number of bits to mask.

MaskType integer between 1 and 32

16

1.3 DSCP-Selection-Table

This contains DSCP selection rules for different media types.

DSCP-Selection-TableType

NA NA

1.3.a DSCP-selection-Rule

This specifies details of each media type.

DSCP-Selection-RuleType

NA NA

1.3.a.i DSCP-Egress

DSCP-Egress specifies the value for quality of service offered for the media flow between IBCF and the peer network.

integer integer between 0 and 63

46

Table 3 Peer network policy parameters

13


2.2.2 Gq-or-Rx-Interface and parametersThis section specifies configuration parameters needed for the Gq or Rx interface of this PCS instance. Gq/Rx (Rx will replace Gq) is the 3GPP interface between PCS and AF(Application Function, e.g., IMS P-CSCF). If the Gq/Rx interface of this PCS instance is not used then this section is irrelevant.Gq-or-Rx host specific configuration parametersFollowing parameters are available in PCS_HostSpecificConfigParams.xml. These parameters doesnt require a process restart after modification. Max-Allowed-Process-ing-Time_m parameter can be dynamically activated.

1.3.a.ii DSCP-Ingress

DSCP-Ingress specifies the value for quality of service offered for the media flow between IBCF and the Core Network.


30

1.3.a.iii Media-Type It specifies the Media Type of the Media stream.

string AUDIO, VIDEO, DATA, APPLICA-TION, CONTROL, TEXT, MESSAGE, OTHER, ANY

AUDIO

1.3.a.iv DSCP-Control

DSCP-Control is used to prioritizes flow of UDP packets for a particular Media type.

boolean true, false true

S.No Parameter name


Table 3 Peer network policy parameters (Cont.)

Parameter name


List-of-Served-AFs

This table lists all the Host-Names of the AFs that are allowed to connect to the PCS. Each Host-Name represents the Diameter identity (fully quali-fied host name) of an allowed AF; this Diameter identity must match the one the AF sends to the PCS in the Gq/Rx Origin-Host AVP.

List-of-Served-AFsType

NA NA

Host-Name-Container

Contains host name related information like host name, peer type and so on.

Hostname-Container-Type

NA NA

Host-Name Host name is the name of the host. It must be a fully qualified host name.

string NA *

Table 4 Gq-or-Rx host specific configuration parameters

14


Peer-Type Lets you specify the peer type. The peer type can be chosen based on the interface, for more infor-mation refer to Appendix 4- Peer-type.

string GGSN, AF_MOBILE, AF_FIXED, GGSN_STARENT, GGSN_ERICSSON, GGSN_CISCO_SCE, SOAP_ONENDS, SOAP_SESSION_TRACKER, AF_NOTIFICATION, BRAS, WLAN

GGSN for Gx; AF_Mobile for Rx

Send-Response-Enabled

This parameter indicates whether to send a Radius-Acct-Response or not. If the value of this parameter is set to false, then the Radius-Acct- Response is suppressed.


Release-Version

The GGSN Release Version is chosen based on the following values:

• REL8: This has precedence over Supported Features AVP and takes the Gx as Release 8 version.


• SUPPORTED_FEATURES: Look at the Sup-ported Features AVP and decide whether Release 8 or Release 9 compliant.

• DEFAULT:If DEFAULT is selected, it means REL7 is supported.

string DEFAULT, REL8, SUPPORTED_FEATURES, REL9

DEFAULT

Session-Level-Moni-toring-Key

It checks for monitoring key if it is same as that in the session level.

g Monitoring-Key can not contain "_".

string NA SES-SION-LEVEL

SiteId It is an identifier to identify the GGSN deployment site.

string NA 0

Parameter name


Table 4 Gq-or-Rx host specific configuration parameters (Cont.)

15


g Refer to Appendix 3 section Gq-or-Rx-Interface for schematic view of Gq-or-Rx interface host specific configuration parameters.Apart from peers which directly connect with PCS (i.e. exchange CER-CEA with PCS), the diameter clients behind a DRA or proxy agent need also to be configured on PCS. This is because the host configurations are expected to be per diameter client being served. Hence ,any value of Origin-Host AVP present in request message(CER,CCR, AAR) from peers need to be configured in PCS_Hostspecificparams.xml

Gq-or-Rx General Configuration Parameters:Following parameters are available in PCS_GeneralConfigParams.xml. These parame-ters require a process restart after modification.

Max-Allowed-Processing-Time_ms

The time value is represented in milliseconds. Configured value indicates the time within which a Gx or Gy transaction (CCR processing and sending CCA) should be completed. If not com-pleted within this time then the respective PDP context will be deleted.This tag is applicable only for Gx and Gy interface. For other interfaces this tag is not used, hence set the value to 0.

g To disable this transaction time-based check, set the parameter to 0.

integer between 1000 and 3600000

0

Qos-Negoti-ation-Sup-ported

This parameter indicates Qos Negotiation is enabled or not. If enabled Qos negotiation is done as per standards, If disabled then no Qos negotia-tion policy evaluated Qos will be sent. This is used only for Gx.

boolean true,false TRUE

APN-Name This parameter will be used for key generation if called-station-id is not present in the incoming message or APN-Override flag is set to true. DEFAULT value will be considered as NULL string.

String NA DEFAULT

APN-Override

If this parameter is true, always the value from APN-Name will be taken for key generation. In case of false the Called-Station-Id received in mes-sage(if present) or value from APN-Name configu-ration (if configured) will be used in order of occurrence.

Boolean true or false false

Parameter name


Table 4 Gq-or-Rx host specific configuration parameters (Cont.)

16


Parameter name


Answer-Timer_ms

This indicates the delay in Milliseconds before which Gx Session state expects an answer for RAR message.


2000

Session-Release-Delay-Timer_ms

When the connection between TCP and peer is lost, “Session-Release-Delay-Timer” starts with the configured value. If the connection is not restored before the expiration of the timer, PCS starts releasing all the sessions created by that peer.

If it is set to 0, the timer will not start after a con-nection loss. Therefore, there will be no session release (disables session release). Dynamic activation of this parameter is not sup-ported.

integer integer between 0 to 9000000

60000

Require-Missing-Service-Info

When PCEF (GGSN) requests authorizing a ded-icated bearer (PDP context, IP channel) and PCS has not got yet sufficient service information for this authorization the Require-Missing-Service-Info indicates whether or not PCS requests service information from AF. It is requested by sending a Gq or Rx message with Specific-Action AVP set to SERVICE_ INFORMATION_ REQUEST.

g If AF has requested the SERVICE_INFORMATION_REQUEST specific-Action for a Gq or Rx session in the initial request of the session then PCS will request service information from AF whenever PCEF requests authorizing a dedicated bearer and this authorization uses service information of that session, independently on this parame-ter and even if PCS has already got sufficient information for the authorization.


Hanging-Session-Detec tion-Timer_h

After the Hanging-Session-Detection-Timer interval is reached PCS checks for existing session in the application layer, for example SIP proxy. If a corresponding session for a non existing session in the application layer exists in the transport layer then it is removed from this layer. A time value of 0 (zero) switches off the Gq synchronization.


12

Table 5 Gq-or-Rx general configuration parameters

17


g Refer to Appendix 2 section Gq-or-Rx-Interface for schematic view of Gq-or-Rx General Configuration Parameters.

2.2.3 Gx-Interface and parametersThis section specifies configuration parameters needed for the Gx interface of this PCS instance. Gx is the 3GPP interface between PCS and PCEF (Policy and Charging Rule Execution Function for example, GGSN). If the Gx interface of this PCS instance is not used, this section is irrelevant.Gx host specific configuration parametersFollowing parameters are available in PCS_HostSpecificConfigParams.xml. These parameters doesnt require a process restart after modification. Max-Allowed-Process-ing-Time_m parameter can be dynamically activated.

Msg-Retry-Limit

Maximum number of times a Msg can be re-sent Integer 0 to 100 1

Allow-Emer-gency-Services-Over-Non-Emergency-Gx

This configuration parameter defines PCS behav-iour when the Rx session indicates that it's an emergency session (Service URN indicating emergency), but the corresponding Gx session is a normal session (not on emergency APN). If true, PCS will allow the Rx call like a normal call. If false, PCS will reject Rx call.

boolean true, false false

List-Of-Emergency-Info

List of Service-URNs based on which the call is identified as an emergency call.Applicable to CPCS scenario only.

Table NA NA

Emergency-Info

Emergency APNs(Called-Station-Id) for Gx inter-face and Emergency Service-URN for Rx inter-face. No default.Applicable to CPCS scenario only.

Container NA NA

Emergency-Id

Value in Called-Station-Id (APN name) AVP in case of gx interface and value in Service-URN AVP incase of Rx interface. Applicable to CPCS scenario only.

string NA NA

List-of-Priority-Identifiers

List of authorised MPS identifiers Table NA NA

Priority-Identifier

Authorised list of MPS Identifier. Container NA NA

Name MPS Identifier from SPR in case of gx interface and MPS_Identifier AVP value incase of Rx inter-face.

string NA NA

Parameter name


Table 5 Gq-or-Rx general configuration parameters (Cont.)

18


S.No Parameter name


1 List-of-Served-PCEFs

This table contains the Host-Names of the PCEFs that are allowed to connect to the PCS. The list consists of fully qualified host names. Each Host-Name represents the Diameter identity of an allowed PCEF; this Diameter identity must match the one of the PCEF sends to the PCS in the Gx Origin-Host AVP.

List-of-Served-PCEFs-Type

NA NA

1.1 Host-Name-Container

Contains host name related informa-tion like host name, peer type and so on.

Hostnam-eContain-erType

NA NA

1.1.1 Host-Name Host name is the name of the host. It is fully qualified host name.

string NA NA

1.1.2 Peer-Type Lets you specify the peer type. The peer type can be chosen based on the interface, for more information refer to Appendix 4- Peer-type.

string GGSN, GGSN_STARENT, GGSN_ERICSSON, GGSN_CISCO_SCE

GGSN

1.1.3 Qos-Negoti-ation-Sup-ported

This parameter indicates whether the Qos negotiation is enabled or not. If it is enabled, the Qos negotia-tion is done as per the standards. If it is disabled, then Qos negotiation policy evaluated Qos is not sent.


1.1.4 Send-Response-Enabled

This parameter indicates whether to send a Radius-Acct-Response or not. If the value of this parameter is set to false, then the Radius-Acct-Response is suppressed.


Table 6 Gx host configuration parameters

19


1.1.5 Release-Version

The GGSN Release Version is chosen based on the following values: • REL8: This has precedence

over Supported Features AVP and takes the Gx as Release 8 version.


• SUPPORTED_FEATURES: Look at the Supported Features AVP and decide whether Release 8 or Release 9 compli-ant.

• DEFAULT: If DEFAULT isse-lected, it means REL7 is sup-ported.

string DEFAULT, REL8, SUPPORTED_FEATURES, REL9

DEFAULT

1.1.6 Session-Level-Moni-toring-Key

It checks for monitoring key if it is same as that in the session level.

string NA SES-SION-LEVEL

1.1.7 Siteid It is an identifier to identify the GGSN deployment site.

string NA 0

1.1.8 Max-Allowed-Processing-Time_ms

The time value is represented in mil-liseconds. Configured value indi-cates the time within which a Gx or Gy transaction (CCR processing and sending CCA) should be com-pleted. If not completed within this time then the respective PDP context will be deleted.

This tag is applicable only for Gx and Gy interface. For other interfaces this tag is not used, hence set the value to 0.

gTo disable this transaction time-based check, set the parameter to 0.


0

S.No Parameter name


Table 6 Gx host configuration parameters (Cont.)

20


g Refer to Appendix 3 section Gx Interface for schematic view of Gx host specific config-uration parameters.Apart from peers which directly connect with PCS (i.e. exchange CER-CEA with PCS), the diameter clients behind a DRA or proxy agent need also to be configured on PCS. This is because the host configurations are expected to be per diameter client being served. Hence ,any value of Origin-Host AVP present in request message(CER,CCR, AAR) from peers need to be configured in PCS_Hostspecificparams.xml.

Gx general configuration parametersFollowing parameters are available in PCS_GeneralConfigParams.xml. These parame-ters require a process restart after modification except Except Send-SNR-For-Unsub-scribe-Indicated and Send-SNR-For-Subscribe-Indicated which are dynamically activated and doesnt require process restart

1.2 Qos-Negoti-ation-Sup-ported

This parameter indicates Qos Nego-tiation is enabled or not. If enabled Qos negotiation is done as per stan-dards , If disabled then no Qos negotiation policy evaluated Qos will be sent.This is used only for Gx.


S.No Parameter name


Table 6 Gx host configuration parameters (Cont.)

Parameter name


Answer-Timer_ms

This indicates the delay in Milliseconds before which Gx Session state expects an answer for RAR message.


2000

Obligation Name

Obligation name in MIP Sync obligations String NA NA

Table 7 Gx general configuration parameters

21


Session-Release-Delay-Timer_ms

This timer set the waiting time for PCS before it releases affected Gx session. When the TCP con-nection between a peer is lost, “Session-Release-Delay-Timer” starts with the configured value. If the connection is not restored before the expiration of the timer, PCS starts releasing all the sessions created by that peer. The time is set in milliseconds. The value should be greater than the maximum Gx reconnection time configured on the PCEFs served by the PCS.If it is set to 0, the timer will not start after a connec-tion loss. Therefore, there will be no session release (disables session release).

Dynamic activation of this parameter is not sup-ported.

integer integer between 0 to 9000000

30000

Per-Bearer-Limit-of-Max-Bandwidth_bps

Limit for the maximum authorized data rate (bits per second) including up-link and down-link for direction of a bearer (PDP context, IP channel); default as specified in TS 29.208 table 7.1.1.2. This limit does not affect all traffic bearers.

integer NA 16000000

Per-Bearer-Default-of-Max-Band-width-UL_bps

It specifies the default for the maximum uplink authorized bandwidth of a bearer (PDP context, IP channel). The bandwidth is set in bits per second. This is used for general purpose bearers and for the initial QoS of all traffic bearers.

integer NA 256000

Per-Bearer-Default-of-Max-Band-width-DL_bps

It specifies the default for the maximum downlink authorized bandwidth of a bearer (PDP context, IP channel). The bandwidth is set in bits per second. This is used for general purpose bearers and for the initial QoS of all traffic bearers.

integer NA 256000

Per-Bearer-Default-QoS-Class

It specifies the default authorized QoS class of a bearer (PDP context, IP channel). This default is used for general purpose bearers and for the initial QoS for all bearers.

string A thru I D

Keep-RTCP-Gates-Always-Open

It specifies whether or not PCS will keep the gates of all RTCP IP flows always open. This parameter overrides all other relevant configuration parameters (incl. Close-Gates-Before-Removal) and flow states in Gq or Rx messages.


Parameter name


Table 7 Gx general configuration parameters (Cont.)

22


Reporting-Level

It specifies whether PCS will send AF charging iden-tifiers (e.g., IMS charging identifiers) or configured rating group numbers in charging rules to PCEF. PCEF uses this information for generating charging records. The value is CHARGING_ RULE_LEVEL or RATING_GROUP_LEVEL. The CHARGING_ RULE_LEVEL sets AF charging identifiers and RATING_GROUP_LEVEL sets rating group numbers.

g This parameter does not affect pre configured charging rules: They always include rating group numbers. For the rating group numbers, see the Rating-Group parameter in the QoS-and-Charging-Selection-Table.

string RATING_GROUP_LEVEL, CHARGING_RULE_LEVEL

RATING_GROUP_ LEVEL

Authorize-QoS

It specifies whether or not PCS will send QoS parameters to PCEF (GGSN).


Remove-After-Timer-UL_s

This timer specifies the waiting time for PCS before it disables the IP flows on the general purpose bearer. The time is set in seconds. When shifting one or more uplink IP flows from a general purpose bearer (PDP context, IP channel) to a dedicated one, PCS will instruct PCEF (GGSN) to delay their removal (disabling) on the general purpose bearer till this time ends, the IP flows are enabled on both bearers for this time.

integer NA 10

Remove-After-Timer-DL_s

This timer specifies the waiting time for PCS before it disables the IP flows on the general purpose bearer. The time is set in seconds. When shifting one or more downlink IP flows from a general purpose bearer (PDP context, IP channel) to a ded-icated one, PCS will instruct PCEF (GGSN) to delay their removal (disabling) on the general purpose bearer till this time ends, the IP flows are enabled on both bearers for this time.

integer NA 10

OFCS-Primary-Address

It specifies the OFCS address. This address must be configured if Send-Charging-Address-Indicated feature is enabled.

string NA OFC-SPrima-ryAddress

OFCS-Sec-ondary-Address

It specifies the secondary OFCS address. This address must be configured if Send-Charging-Address-Indicated feature is enabled.

string NA OFCS-Second-aryAddress

Parameter name



23


OCS-Primary-Address

It specifies the primary OCS address. This address must be configured If Send-Charging-Address-Indi-cated feature is enabled.

string NA OCSPri-maryAd-dress

OCS-Sec-ondary-Address

It specifies the secondary OCS address. This address must be configured If Send-Charging-Address-Indicated feature is enabled.

string NA OCS-Second-aryAddress

Send-Charging-Address-Indicated

If this feature is enabled then PCRF will send config-ured charging addresses otherwise the pre config-ured Charging address in PCEF is used.

g PCRF can override the pre configured Charging address in PCEF.


Send-Online-Charging-Method-Indicated

If this feature is enabled then PCRF will send config-ured charging method else the preconfigured Charging method in PCEF is used.

g PCRF can override the preconfigured Charging method in PCEF.


Send-Offline-Charging-Method-Indicated

If Send-Charging-Method-Indicated feature is enabled then this charging method may be config-ured.


Use-GGSN-Local-Rules

If this field is enabled, then PCS will send DIAMETER_AUTHORIZATION_REJECTED(5003), in case of subscriber not configured in database. If it is disabled, PCS will send USER_UNKNOWN(5030) error code.In case there are no services configured for the subscriber, PCS doesnot send Charging-Rule-Remove for the services listed in Charging-Rule-Report.


Online-Charging-Method

If Send-Charging-Method-Indicated feature is enabled then this charging method may be config-ured.

string ENABLE_ONLINE, DISABLE_ONLINE

ENABLE_ ONLINE

Offline-Charging-Method

If Send-Charging-Method-Indicated feature is enabled, then this charging method may be config-ured

string ENABLE_ OFFLINE, DISABLE_ OFFLINE

ENABLE_ OFFLINE

Delay-Timer-for-Bearer-Release

This timer specifies the waiting time after which PCS re-connects to a NASS once a connection to the NASS has failed. The time is specified in millisec-onds.


5000

Parameter name



24


Wait-For-CCR

This timer specifies the waiting time for PCS after which it start sending RAR (unsolicited Provision-ing). The time is specified in milliseconds.


20000

SGSN-Change

If SGSN-Change is enabled then this Event Trigger is activated.


Out-of-Credit

If Out-of-Credit is enabled then this Event Trigger is activated.


Qos-Change

If Qos-Change is enabled then this Event Trigger is activated.


Default-EPS-Bearer-QoS-Change

If Default-EPS-Bearer-QoS-Change is enabled then this Event trigger is activated.


RAT-Change

If RAT-Change is enabled then this Event Trigger is activated.


TFT-Change

If TFT-Change is enabled then this Event Trigger is activated.


PLMN-Change

If PLMN-Change is enabled then this Event Trigger is activated.


Loss-of-Bearer

If Loss-of-Bearer is enabledthen this Event Trigger is activated.


Recovery-of-Bearer

If Recovery-of-Bearer is enabled then this Event Trigger is activated.


IP-CAN-Change

If IP-CAN-Change is enabled then this Event Trigger is activated.


GW-PCEF-Malfunction

If GW-PCEF-Malfunction is enabled then this Event Trigger is activated.


Resource-Limitation

If Resource-Limitation is enabled then this Event Trigger is activated.


MAX-NR-Bearers-Reached

If MAX-NR-Bearers-Reached is enabled then this Event Trigger is activated.


Qos-Change-Exceeding-Authoriza-tion

If Qos-Change-Exceeding-Authorization is enabled then this Event Trigger is activated.


RAI-Change

If RAI-Change is enabled then this Event Trigger is activated.


Parameter name



25


User-Location-Change

If User-Location-Change is enabled then this Event Trigger is activated.


Send-ARP-Indicated

If Send-ARP-Indicated is enabled then the ARP is send with CCA.


Send-SNR-For-Sub-scribe-Indi-cated

If Send-SNR-For-Subscribe-Indicated is enabled. Then SNR-register will be sent by CCR-Initial

boolean true, false TRUE

Send-SNR-For-Unsub-scribe-Indi-cated

If Send-SNR-For-Unsubscribe-Indicated is enabled then SNR-Deregister is sent by CCR-Terminate.


Realloca-tion-Of-Credit

If Reallocation-Of-Credit is enabled then this Event Trigger will be activated.


Msg-Retry-Limit

This indicates the number of times a message origi-nated from PCS like RAR (Re-Authorization-Request)/ASR (Abort-Session-Request) should be retried in case there is no response from the other connected network element for the corresponding message.

A message will be retried until a response is received or the number of retries has reached the configured value (whichever occurs first). The messages which are retried will have the T-poten-tially Retransmitted bit set according to Diameter 3588 specificaiton.


1

User-Agent-Type-Trigger

If the UserAgent trigger is enabled, then this Event Trigger will be activated.


Hanging-Session-Detection-Timer_h

After the Hanging-Session-Detection-Timer interval the PCS checks whether the session is still existing. On this timer expiry RAR will be triggered. On failure response of RAA session will be removed

Integer 0 to 60 0

Allow-Emer-gency-Services-Over-Non-Emergency-Gx

This configuration parameter defines PCS behav-iour when the Rx session indicates that it's an emer-gency session (Service URN indicating emergency), but the corresponding Gx session is a normal session (not on emergency APN). If true, PCS will allow the Rx call like a normal call. If false, PCS will reject Rx call.


Parameter name



26


g 1. Keep-RTCP-Gates-Always-Open and Close-Gates-Before-Removal are depre-cated parameters.

2. Refer to Appendix 2 section Gx Interface for schematic view of Gx general configu-ration parameters.

3. The time interval for each message retry is calculated as follows:Retry-Interval=Answer-Timer*2(Retry-Count)

where Answer-Timer is available in PCS_GeneralConfigParams.xml under the respective interface configuration. Retry-count is an integer value; it will be 0 for the first message, 1 for the second message, and so on.In Gx or Rx scenario once the Retry-Limit has reached the configured value, a message is sent to the CORE process group indicating the expiration of the timer, to assist the core process to take further relevant actions.For Gx-Rx scenarios, it is suggested to keep the Msg-Retry-Limit to 1. If it needs to be greater than 1, accordingly the context expiration timer value needs to be adjusted.

2.2.4 SPR-Search-InfoLists all the host configuration related SPR information for this interface.

SPR host specific configuration parameters:Lists all the host configuration related SPR information for this interface.

2.2.5 Sh-Interface and parametersLists all the host configuration parameter for the sh interface.Sh host specific configuration parametersFollowing parameters are available in PCS_HostSpecificConfigParams.xml. These parameters require a process restart after modification.

ARP-Priority-Level

It is a comma (,) separated values of priority levels (1 through 15, both inclusive).

String NA NA

Parameter name



S.No Parameter name


1 Compare-Key-Name

This specifies the compare key for the search info.

Compare-Key-NameType

IMSI, MSISDN, SIP_URI

IMSI

2 Compare-Key-Type

This specifies the compare key type to be used.

Compare-Key-TypeType

RANGE, BEST_MATCH, EXACT_MATCH, APR_NAME

BEST_ MATCH

Table 8 SPR host specific configuration parameters

27


S.No Parameter name


1 Table-of-IMEI-Ranges

This specifies IMEI ranges for device.

Table-of-IMEI-Ranges-Type

NA NA

1.1 IMEI-Range It’s a list of IMEI-Ranges. IMEI-Range-Type

NA NA

1.1.a IMEI It sets a unique IMEI ID. IMEIType NA 123

1.1.b Device It is a unique device for an unique IMEI.

DEVICE-TYPE

NA Nokia

2 Table-of-Device-Types

This specifies devices supported by subscriber.

Table-of-Device-Types-Type

NA NA

2.1 Device-Types

Contains device relates informa-tion.

Table-of-Device-Types-Type

NA NA

2.1.a Version It specifies the device version. DeviceVer-sionType

NA 1.0

2.1.b Device It sets the device value. DeviceDef-initionType

NA Nokia

2.1.c Action It sets the action to be taken. It can be allow or block or control.

DeviceAc-tionType

allow, block, control allow

3 Table-of-Served-HSSs

This specifies the supported HSSs Table-of-Served-HSSs-Type

NA NA

3.1 HSS Each HSS entry includes either it’s fully qualified host name or IP address. IPv4 address is in a dotted decimal format and IPv6 address in textual format as described in RFC 3513. If the table includes host names then PCS must be served by a DNS server. Each NASS entry includes the port number on that the ARACF listens for e4 TCP connections and a list that specifies the range the ARACF supports

HSSType NA NA

Table 9 Sh interface host specific configuration parameters

28


3.1.a SPR-Name It specifies the name of the SPR. SPR-NameType

NA HSS1

3.1.b Host-Name Host name is the name of the host and it is the fully qualified host name.

string NA blrmimsws01

3.1.c IP-Address It represents an IP Address. IPv4 address is in a dotted decimal format and IPv6 address in textual format as described in RFC 3513Example for IPv4: 130.12.2.0Example for IPv6: 12AB:0:0:CD3.

IPAddress-Type

IPv4, IPv6 132.186.71.140

3.1.d Port It specifies the port used. PortType integer between 0 and 65535

1833

3.1.e Service-Indication-ID

Represents the ID of service String NA PCS

3.1.f Domain-Name

It represents the Hss domain name.

string NA 3gppnetwork.org

3.1.f SPR-Access-Mode

The SPR data is stored in the session context as a cache and updated on SPR triggers.Configure SPR-Access-Mode for each SPR as RAWA, ROWO and ROWA.RAWA means Read Always, Write Always.ROWO means Read Once, Write Once.ROWA means Read Once, Write Always.

string RAWA, ROWO, ROWA

RAWA

3.2 List-of-Ranges

Lists all the IMSI ranges. List-of-Ranges-Type

NA NA

3.2.1 Range Contains range related information Range-Type

NA NA

3.2.1.a Initial-Value It specifies the starting value for the range.

Initial-Valu-eType

NA 0

3.2.1.b Final-Value It specifies the ending value for the range.

Final-Valu-eType

NA 1

3.3 List-of-Prefixes

Lists the allowed prefixes. List-of-Pre-fixesType

NA NA

S.No Parameter name


Table 9 Sh interface host specific configuration parameters (Cont.)

29


g Refer to Appendix 3 section Sh-Interface for schematic view of Sh Host Specific Config-uration Parameters.

Sh general configuration parameters:Following parameters are available in PCS_GeneralConfigParams.xml. These parame-ters require a process restart after modification.

3.3.1 Prefix-Con-tainer

Contains all the prefix related infor-mation.

Prefix-Container-Type

NA NA

3.3.1.a Prefix It specifies the prefix used. PrefixType NA NA

3.4 List-of-Exact-Matches

Lists all the exact matches List-of-Exact-Matches-Type

NA NA

3.4.1 Exact-Match-Con-tainer

it’s a container that stores all the exact matches

Exact-Match-Container-Type

NA NA

3.4.1.a ExactMatch Specifies the exact match string. string NA NA

S.No Parameter name


Table 9 Sh interface host specific configuration parameters (Cont.)

S.No Parameter name


1 Answer-Timer_ms

This indicates the delay in Millisec-onds before which Gx Session state expects an answer for RAR message.

Answer-Timer_msType


2000

2 Postpaid-Policy-Enabled

It enables or disables the POSTPAID policy.


3 Prepaid-Policy-Enabled

It enables or disables the PREPAID policy.


4 SmartLim-its-Policy-Enabled

It enables or disables the SMART LIMITS policy.


5 Service Specific Roaming-Policy-Enabled

It enables or disables the ROAMING policy.


Table 10 Sh general configuration parameters

30


2.2.6 LDAP-Interface and parametersThis section specifies the configuration parameters needed for the Ldap interface of this PCS instance. If the Ldap interface of this PCS instance is not used then this section is irrelevant. One-NDS parameters can be dynamically updated. A restart of the IMS_G_PCS_LDAP group on ADV GUI is required to reflect the changes.LDAP host configuration parametersFollowing parameters are available in PCS_HostSpecificConfigParams.xml. These parameters require a process restart after modification except SPR-Access-Mode parameter which is dynamically activated and requries process restart.

6 Service Activation-Policy-Enabled

It enables or disables the SERVICE ACTIVATION policy.


7 Automated-Promotions-Policy-Enabled

It enables or disables the PROMO-TIONS policy.


8 Subscrip-tion-Retry-Timer_min

Indicates the retry timer for sub-scription.

Integer NA 1

9 List-of-denied-IMEIs

Lists all the denied IMEIs. Listofde-niedIMEIs-Type

NA NA

9.1 IMEI-Con-tainer

It contains all the IMEI numbers in the denied list.

IMEICon-tainerType

NA NA

9.1.1 IMEI IMEI number in the denied list. IMEIType NA NA

S.No Parameter name


Table 10 Sh general configuration parameters (Cont.)

S.No Parameter name


1 Table-of-LDAPs

Lists all the LDAP servers. Table-of-LDAPs-Type

NA NA

1.1 LDAP Contains information on LDAP interface data like SPR name, LDAPBaseDN, userdn, pass-words, ip address, port, host priority and so on.

LDAPType NA NA

Table 11 LDAP host configuration Parameters

31


1.1.1 SPR-Name It specifies the name of the LDAP. SPR-NameType

NA LDAP1

1.1.2 LDAP-BaseDN

It specifies the LDAP Base Distin-guished Name (DN)

string NA dc=C-NTDB

1.1.3 UserDN It is the user name to connect to a LDAP server.

string NA cn=sdfrun

1.1.4 UserPW It specifies the password used to connect to a LDAP server.

gSpecial characters <, >, &, and ^ are not allowed in the pass-word.

Password-Type

NA sdfrun1

1.1.5 LDAPHost-Priority

It sets the host priority. Integer integer between 0 and 65535

1

1.1.6 LDAPHost It specifies the IP address of the LDAP host.

IPv4AddressType

IPv4 1.1.1.1.

1.1.7 LDAPPort It specifies the server port where the LDAP server is running.

Integer integer between 1 and 65535

16611

1.1.8 SPR-Access-Mode

The SPR data is stored in the session context as a cache and updated on SPR triggers depend-ing on the SPR-Access.RAWA means Read Always, Write Always.ROWO means Read Once, Write Once.ROWA means Read Once, Write Always.

string ROWO, ROWA, RAWA

RAWA

1.2 List-of-NSRData

Contains non subscriber related information.

List-of-NSRData-Type

NA NA

1.2.1 NSRData It provides the list of Non-sub-scriber related data.

NSRData-Type

NA NA

S.No Parameter name


Table 11 LDAP host configuration Parameters (Cont.)

32


1.2.1.a NsrSearchRDN

LDAP Service Indication RDN for non-subscriber-related (NSR) data

string • ds=DEVICE,o=DEFAULT, dc=CNTDB

• o=pcsServiceN-ode, o=pcs,o=NSS,o=services, o=DEFAULT,dc=C-NTDB

• o=pcsQoS,o=pcs,o=NSS,o=ser-vices, o=DEFAULT, dc=C-NTDB

NA

1.2.1.b NsrSearch-Key

It sets the search key for Nsr search.

string tac, pcsServiceId, pcsQosProfName

tac

1.2.1.c SearchFlag It sets the search flag status. boolean true, false true

1.2.1.d NsrObject-Class

It specifies the nsr object class to use.

string deviceType2g3g, pcsServiceNode, pcsQos

NA

1.3 List-of-Ranges

It contains all the range of IMSI, MSISDN.

List-of-Ranges-Type

NA NA

1.3.1 Range It contains IMSI, MSISDN range specific information.

NA NA NA

1.3.1.a Initial-Value It sets the start value of range Initial-Valu-eType

NA NA

1.3.1.b Final-Value It sets the end value of the range integer NA NA


Lists the allowed prefixes List-of-Pre-fixesType

NA NA



Final-Valu-eType

NA NA

1.4.1.a Prefix It specifies the prefix used or wild-card.

string NA *


Lists the exact matches. List-of-Exact-Matches-Type

NA NA

S.No Parameter name



33


Restrictions1. During LDAP double fault, the minimum time taken to respond to the CCA will be at

least equal to the LDAP-Read-Timeout_s value.2. there will be a huge MRT (approximately 10 seconds, if the LDAP-Read-Timeout_s

is set to 10 seconds) towards GGSN during LDAP double fault time. Therefore, chances of requests getting timed out in GGSN for these calls are high. This will result in call failure for the user.

3. The LDAP-Read-Timeout_s should not be configured more than the Health-Check-Time-Out parameter (in ADV-GUI), otherwise the LDAP process will restart.

4. If a wrong LDAP IP or No LDAP is configured in the Host Specific Config Files, then LDAP goes down immediately after it is brought down.

5. If a Valid LDAP IP is configured, then LDAP takes approximately time configured in LDAP_Read_Timeout_s (in PCSBasicConfigParams.xml) to go down.

Recommendations1. To avoid requests timing out at GGSN, the LDAP-Read-Timeout_s must be config-

ured in-line with timeout value for CCA at GGSN.2. To keep the MRT less, it is recommended to configure the LDAP-Read-Timeout_s

with a smaller value.

2.2.6.1 LDAP parameters in basic configuration fileThis section lists the LDAP parameters available in PCS Basic Configuration parame-ters file in /opt/PCS/config/PCS_BasicConfigParams.xml.


It contains all the exact matches being used.


NA NA

1.5.1.a ExactMatch It specifies the exact match string used.

Exact-MatchType

NA NA

S.No Parameter name



S.No Parameter name


1 LDAP-Inter-face

Contains the LDAP interface data. NA NA NA

1.1 LDAPRequestTimeout_s

Sets the time limit till which a stage can remain valid. It is the generic type for authorized, reserved, com-mitted, and committed recovery. Time is set in seconds.


5 second

Table 12 LDAP basic configuration parameters

34


2.2.7 Common parametersThis section describes the various attributes of the common details.Common host configuration parameters:Following parameters are available in PCS_HostSpecificConfigParams.xml. These parameters require a process restart after modification except Table-of-Subscriber-To-Trace parameter which is dynamically activated and requires process restart.

1.2 LDAPReconnectTimer_s

Sets the time limit till which a stage can remain valid. It is the generic type for authorized, reserved, com-mitted, and committed recovery. Time is set in seconds.


5 seconds

1.3 LDAPNo-ConnectionTimer_s

Time in seconds where dummy LDAP request is sent to One-NDS.

g This value shall be less than LDAP-Read-Timeout_s always.


5 seconds

1.4 LDAP-Read-Timeout_s

Time in seconds where LDAP API times out waiting for response from One-NDS.

g • It must be always greater than LDAPNoConnectionTimer_s (ideally 3 times the LDAPNoConnectionTimer_s).

• The LDAP-ReadTimeout_s is the maximum time to get the LDAP Connection Down Alarm (239-20) during LDAP double fault.


15 seconds

S.No Parameter name


Table 12 LDAP basic configuration parameters (Cont.)

S.No Parameter name


1 Table-Of-Realm

This table describes various attri-butes required for the realm.

Table-Of-Realm-Type

NA NA

1.1 Realm-Details

Contains realm related information. NA NA NA

Table 13 Common host configuration parameters

35


1.1.1 Realm-Name

It specifies the name of the realm. string NA Realm1

1.1.2 List-of-Hosts

Contains host related information. List-of-HostsType

NA NA

1.1.2.a Host-Details Contains host related information like host name, ip address, port and so on.

Host-Detail-sType

NA NA

1.1.2.a.i Host-Name It specifies the fully qualified host name.

string NA Hostname1

1.1.2.a.ii IP-Address It represents an IP Address. IPv4 address is in a dotted decimal format and IPv6 address in textual format as described in RFC 3513

IPAddress-Type

IPv4, IPv6 255.2.2.1

1.1.2.a.iii Port It’s the port number used. Integer 0 - 65535 3868

2 Table-Of-QCIs

It contains QCI related information. Table-Of-QCIsType

NA NA

2.1 QCI It contains QCIs. QCIType NA NA

2.1.1 Max-Band-width-UL

It sets the maximum uplink band-width.

integer 0-4294967295 2560000

2.1.2 Max-Band-width-DL

It sets the maximum downlink band-width.

integer 0-4294967295 2560000

2.1.3 Guaran-teed-Band-width-UL

It sets the guaranteed uplink band-width.

integer 0-4294967295 20000

2.1.4 Guaran-teed-Band-width-DL

It sets the guaranteed downlink bandwidth.

integer 0-4294967295 20000

2.1.5 Class It sets the QoS Class Identifier. string A thru I A

2.1.6 ARP-Value It sets the allocation retention priority (ARP) value.


1

2.1.7 Pre-Emption-Capability

It sets the pre emption capability. integer integer 1 or 2 0

2.1.8 Pre-Emption-Vulnerability

It sets the pre emption vulnerability. integer NA 0

S.No Parameter name


Table 13 Common host configuration parameters (Cont.)

36


2.2.8 SPR Interface and parametersThis section specifies configuration parameters related to SPR interface.

SPR service specific configuration parameters:

2.1.9 APN-AMBR-UL

This is the maximum possible UL bit rate configured by the operator for a particular user for all non-Guaran-teed services on one particular Packet Data Network (as defined by the APN).

integer 0-4294967295 2560000

2.1.10 APN-AMBR-DL

This is the maximum possible DL bit rate configured by the operator for a particular user for all non-Guaran-teed services on one particular Packet Data Network (as defined by the APN).

integer 0-4294967295 2560000

2.1.11 QoS-Profile-Name

It sets the QoS profile name. string NA qos1

3 Table-of-Subscriber-To-Trace

List of subscribers to trace Table-of-Sub-scriber-To-Trace type

NA NA

3.1 Trace-Sub-scriber

NA NA NA NA

3.1.1 Subscriber-Id

A unique IMSI id string IMSI NA

S.No Parameter name


Table 13 Common host configuration parameters (Cont.)

S.No Parameter name


1 List-of-MCC-MNC

It contains one or more configured MCCMNC values.

List-of-MCC-MNC-Type

NA NA

1.1 MCCMNC-container

It contains list of MCC-MNC values. MCCMNC-Container-Type

NA NA

1.1.1 MCCMNC it contains a MCCMNC value, which should be six digits

MCCMNC-Type

NA NA

Table 14 SPR service specific configuration parameters

37


For MNC of 3 bytes, consider MCC is 123 and MNC is 456, then MCC-MNC is config-ured as 123456.For MNC of 2 bytes: consider MCC is 123 and MNC is 45, then MCC-MNC is configured as 123045.Example:

PCS has some MCCMNC configured (say 123456,123045,12345,345678) in PCS_Serviceconfig.xml. Consider that the incoming CCR has the IMSI of value 123456789127689. PCS extracts initial 6 digits(123456) and it is compared with the MCCMNC configured in PCS_Serviceconfig.xml. If it matches, PCS considers MNC length as 3 bytes. If it does not match, PCS extracts first 5 digits(12345) and inserts one zero between MCC and MNC(123045). PCS searches the new value 123045 in the con-figured MCCMNC values. If it matches, PCS considers MNC length as 2 bytes. Other-wise, the value configured inside "MNC-Length" (in PCS_Serviceconfig.xml) is considered as the length of MNC.

2.2.9 USPR parameter in Hostspecificconfigparams fileUSPR parameters are configure in SPR-interface.

S.No Parameter name


1 List-Of-USPRs

It specifies the USPR types for device.

Table-of-USPR-Type

NA NA

1.1 USPR It contains USPR related informa-tion. Any changes in this requires restart of the core.

USPRType NA NA

1.1.1 SPR-Name It specifies the name of the SPR. SPR-NameType

NA PAA_test

1.1.2 SPR-Access-Mode

The SPR data is stored in the session context as a cache and updated on SPR triggers.Configure SPR-Access-Mode for each SPR as ROWO and ROWA.ROWO means Read Once, Write Once.ROWA means Read Once, Write Always.

string ROWO, ROWA ROWO

2.1 Application-Id

USPR Application Data related Information

String NA 4

2.2 Service-Context-Id

USPR Application Data related Information

String NA [email protected]

Table 15 USPR host configuration parameters

38


2.2.10 Smpp-Interface and parametersThis section specifies configuration parameters needed for the Smpp interface of this PCS instance.Smpp host configuration parameters:Following parameters are available in PCS_HostSpecificConfigParams.xml. These parameters require a process restart after modification.

3.2 List-of-Ranges

Lists all the IMSI, MSISDNranges. List-of-Ranges-Type

NA NA

3.2.1 Range Contains range related information Range-Type

NA NA

3.2.1.a Initial-Value It specifies the starting value for the range.

Initial-Valu-eType

NA NA

3.2.1.b Final-Value It specifies the ending value for the range.

Final-Valu-eType

NA NA


Lists the allowed prefixes. List-of-Pre-fixesType

NA NA



Prefix-Container-Type

NA NA

3.3.1.a Prefix It specifies the prefix used. PrefixType NA NA


Lists all the exact matches List-of-Exact-Matches-Type

NA NA


it’s a container that stores all the exact matches


NA NA

3.4.1.a ExactMatch Specifies the exact match string. string NA NA

S.No Parameter name


Table 15 USPR host configuration parameters (Cont.)

S.No Parameter name


1 Table-of-SMSC

It specifies the SMSC types for device.

Table-of-SMSC-Type

NA NA

Table 16 Smpp host configuration parameters

39


1.1 SMSC It contains SMSC related informa-tion like smsc ip address, port, system id, password, system type, service type, ESME address and so on.

SMSCType

NA NA

1.1.2 Smsc-ip-address

It specifies the IP for device, it is an IPv4 address.

IPv4AddressType

IPv4 10.255.6.233

1.1.3 Smsc-port It specifies the listening port at device.

Smsc-port-Type

NA 2775

1.1.4 System-Id This is used to identify an ESME or an SMSC at bind time. An ESME system_id identifies the ESME or ESME agent to the SMSC. The SMSC system_id provides an iden-tification of the SMSC to the ESME.

System-Id-Type

NA sysid

1.1.5 Password This parameter is used by the SMSC to authenticate the identity of the binding ESME. The Service Provider may require ESME’s to provide a password when binding to the SMSC. This password is normally issued by the SMSC system administrator..

gThe password parameter may also be used by the ESME to authenticate the identity of the binding SMSC.

Password-Type

NA pwd

1.1.6 System-Type

This parameter is used to catego-rize the type of ESME that is binding to the SMSC.

gSpecification of the system_type is optional - some SMSC’s may not require ESME’s to provide this detail. In this case, the ESME can set the system_type to NULL.

System-type-Type

NA systype

1.1.7 Service-Type

It specifies the service type. SmppSer-viceType-Type

VMA, CMT, CPT, VMN, WAP, USSD, CPS, GUTS

CMT

S.No Parameter name


Table 16 Smpp host configuration parameters (Cont.)

40


SMPP general configuration parameterFollowing parameters are available in PCS_HostSpecificConfigParams.xml. These parameters require a process restart after modification.

1.1.8 Source-ESME-address

It specifies the Source-ESME address types for device.

Source-ESME-address-Type

NA 0

1.1.9 Interface-Version

This parameter is used to indicate the version of the SMPP protocol.

integer NA NA

1.1.10 Source-Addr-Ton

Addr-Ton-Type can take the follow-ing values: UNKNOWN, INTERNA-TIONAL, NATIONAL, NETWORK, SUBSCRIBER, ALPHANUMERIC, ABBREVIATED.

string UNKNOWN, INTERNATIONAL, NATIONAL, NETWORK, SUB-SCRIBER, ALPHA-NUMERIC, ABBREVIATED

UNKNOWN

1.1.11 Source-Addr-Npi

Addr-Npi-Type can take the follow-ing values: UNKNOWN, E164, DATA, TELEX, MOBILE, NATIONAL, PRIVATE, ERMES, INTERNET, WAP.

string UNKNOWN, E164, DATA, TELEX, MOBILE, NATIONAL, PRIVATE, ERMES, INTERNET, WAP

UNKNOWN

1.1.12 Dest-Addr-Ton

Addr-Ton-Type can take the follow-ing values: UNKNOWN, INTERNA-TIONAL, NATIONAL, NETWORK, SUBSCRIBER, ALPHANUMERIC, ABBREVIATED.

string UNKNOWN, INTERNATIONAL, NATIONAL, NETWORK, SUB-SCRIBER, ALPHA-NUMERIC, ABBREVIATED

UNKNOWN

1.1.13 Dest-Addr-Npi

Addr-Npi-Type can take the follow-ing values: UNKNOWN, E164, DATA, TELEX, MOBILE, NATIONAL, PRIVATE, ERMES, INTERNET, WAP.

string UNKNOWN, E164, DATA, TELEX, MOBILE, NATIONAL, PRIVATE, ERMES, INTERNET, WAP

UNKNOWN

1.1.14 Protocol-Id It represents the Protocol-Id-Type. integer NA 0

1.1.15 Registered-Delivery

The registered_delivery parameter is used to request an SMSC delivery receipt and/or SME originated acknowledgments.

integer NA 0

1.1.16 Data-Coding

It represents the Data-Coding-Type. integer NA 0

S.No Parameter name


Table 16 Smpp host configuration parameters (Cont.)

41


2.2.11 Plugin-Interface and parametersThis section specifies configuration parameters needed for the Plugin interface of this PCS instance. If the Plugin interface of this PCS instance is not used, this section is irrel-evant.Plugin host configuration parameters:Following parameters are available in PCS_HostSpecificConfigParams.xml. These parameters require a process restart after modification.

Parameter name Description Type Value range Default

EnquireLinkTrigger_s EnquireLinkTrigger specifies the time after which PCS would trigger an enquire_link message to SMSC. Time is specified in seconds

Integer 0-2147483647 600

EnquireLinkTimer_s EnquireLinkTimer specifies the time interval during which PCS is expecting an enquire_link_resp message from SMSC. Time is specified in seconds

Integer 0-2147483647 5

BindResponseTimer_s BindResponseTimer_s specifies the time for which PCS should wait for Bind Response message from SMSC. Time is specified in seconds

Integer 0-2147483647 2

Table 17 Smpp general configuration parameters

S.No Parameter name


1 List-Of-Plugins

It specifies the available plugins. List-Of-Plugins-Type

NA NA

1.1 Plugin It contains the plugin details. PluginType NA NA

1.1.1 Plugin-ID It is a unique value that identifies the plugins that are present.

integer NA 0

1.1.2 Plugin-Class-Name

It specifies the full path name of the plugin JAVA class.

string NA NA

1.1.3 Plugin-Type It specifies the type of plugin. string REPORTING, DBA_NSR_DATA, TRIGGER_NSR_DATA, DBA_SPR_DATA, TRIGGER_PROFILE_CHANGE

REPORTING

Table 18 Plugin host configuration parameters

42


2.2.12 SOAP-Interface and parametersThis section includes configurations for Multiple SOAP client support for notification trig-gering. It specifies configuration parameters needed for the SOAP interface of this PCS instance. If the SOAP interface of this PCS instance is not used, this section is irrelevant.SOAP host configuration parameters:Following parameters are available in PCS_HostSpecificConfigParams.xml. These parameters require a process restart after modification.

2.2.13 Generic-Notification-Interface and parametersLists all the general configuration parameters for the interface.General configuration parameters:Following parameters are available in PCS_GeneralConfigParams.xml. These parame-ters require a process restart after modification.

1.1.4 Plugin-JarFile

It specifies the file name of the plugin jar. All Jar files has to be con-figured in "/opt/SMAW/INTP/java/"

string /opt/SMAW/INTP/java

NA

S.No Parameter name


Table 18 Plugin host configuration parameters (Cont.)

S.No Parameter name


1 List-of-Soap-Clients

This specifies list of SOAP Clients. List-of-Soap-Clients-Type

NA NA

1.1 Soap-Client It contains the SOAP Client Data. SoapCli-entType

NA NA

1.1.a Do-SPR-Read

Set the value to true if SPR should be read after the trigger is received.

Boolean True, False True

1.2 Host-Name-Container

It contains the host name related information like host name, peer type and so on.

Hostname-Container-Type

NA NA

1.2.a Host-Name It contains the fully qualified host names. After changing the host name PCS restart is required.

String NA *

1.2.b Peer-Type Lets you specify the peer. The peer can be chosen based on the SOAP interface

String SOAP_ONENDS, SOAP_SESSION_TRACKER

SOAP_ONENDS

Table 19 SOAP host configuration parameters

43


2.2.14 Core general configuration parametersFollowing parameters are available in PCS_GeneralConfigParams.xml. These parame-ters are dynamically activated and doesnt require a process restart after modification.

Parameter name


GenericNo-tificationPl-ugin-ClassPath

It specifies the path of the Generic-NotificationPlugin jar file.

string NA /opt/SMAW/INTP/java//GenericNotificationPl-ugin.jar

GenericNo-tificationPl-ugin-ClassName

This is the name of the class file which the configured GenericNotifi-cationPlugin-JAR is containing.

g The configured class file must implement the required default methods.

g PCS provides a default notifica-tion JAR with the name Gener-icNotificationPlugin.jar at path /opt/SMAW/INTP/java. If this JAR file is not used and a cus-tomized jar is going to be used then the name of that custom-ized JAR must be different (other than GenericNotification-Plugin.jar).

string NA GenericNotificationPl-ugin

Table 20 Generic-Notification-Interface general configuration parameters

Parameter name


Volume-Round-Off-Value

It indicates the round off volume to the set value. integer NA 1

Volume-Round-Off-Unit

It Indicates the unit to which the volume needs to be rounded off. It sets to certain value.

string BYTES, KBYTES, MBYTES, GBYTES, TBYTES

BYTES

Graceful-Shutdown-Type

Enables or disables graceful shutdown. If set to false graceful shutdown is not enabled. If set to true then graceful shutdown is enabled and die out and tear down process are executed.


Gs-Dieout-Phase-timer

Sets the timer for dieout phase. integer integer between 0 and 10000

6000

Table 21 Core general configuration parameters

44


g Refer to Appendix 2 section Core for schematic view of Core General Configuration Parameters.

Subscriber-Level-Tracing-Enabled

This parameter indicates whether the subscriber level tracing is enabled or not.


Update-Lookup-Context

Decides whether update to LOOKUP context is needed or not.

false = (default value) means the LOOKUP context will not be updated

true = means LOOKUP context will be updated always


Parameter name


Table 21 Core general configuration parameters (Cont.)

45


2.2.15 Attribute parametersFollowing parameters are available in PCS_Attributes.xml. These parameters are dynamically activated and doesnt require a process restart after modification.

S.No Parameter name


1 List-of-Attri-butes

Lists all the attributes defined by the operator which are used in the access rules.

List-of-Attributes-Type

NA NA

1.1 Attribute Contains attribute related informa-tion like attribute name, type, id, data type, object class name, SPR interface and so on.

Attribute-Type

NA NA

1.2 Attribute-name

It specifies the name for the new attribute. Attribute name is used as attribute Id in access rules.

gCharacters that can be used for naming are restricted to alphabets, underscore and hyphen.

string [_A-Za-z0-9\-]+ NA

Table 22 Attribute parameters

46


1.3 Type It is used for defining policies by accessrules. It specifies the attri-bute type. It can be • INTERFACE: INTERFACE

attributes are related to the diameter incoming request.

• PROFILE: PROFILE attributes are related to subscriber data taken from the different SPRs. For PROFILE attributes, SPR-Interface is either , Sh-Inter-face or Local-DB-Interface.

• SESSION: SESSION attri-butes are defined by the operator and are available for the lifetime of the Session only.

• PROFILE_NSR: PROFILE_NSR attributes are available in the NSR data. For PROFILE_NSR attribute.

• REPORTING: If any interface attribute needs to be reported, it should have two entries for that attribute in Attri-bute.xml.One with Atttribute set to INTERFACE (for PRE) and the other set to REPORT-ING (for reporting).

• PLUGIN_NSR: • PROFILE_SESSION: This

indicates that the attribute is used to store the Session Data. PCS does not send the PROFILE_SESSION attri-butes for policy evaluation.

• PLUGIN_NSR: these attri-butes are retrieved from the NSR data received from the NSR Plugin

string INTERFACE, PROFILE, PROFILE_NSR, SESSION, REPORTING, PROFILE_SESSION, PLUGIN_NSR

PROFILE

S.No Parameter name


Table 22 Attribute parameters (Cont.)

47


1.4 Id It specifies the ID corresponding to an existing database parameter. This parameter is retrieved for the attribute. For example, for INTER-FACE type attribute, ID is as per dictionary.xml definition. For PROFILE type, it is the name of field according to the data model.

string [_A-Za-z0-9\-.$ ]+ NA

1.5 Datatype It specifies the data type for the database parameter. This param-eter must exist in the database and is retrieved for the attribute.

Datatype-Type

integer, string, double, dateTime

integer

1.6 Object-ClassName

It specifies the object class name of the input attribute ID.

gObjectClassName not applica-ble in NonNSRdata.

Object-Class-NameType

NA NOT_APPLICABLE

1.7 Interface It specifies the interface to which the attribute belongs to.

g • Plugin-Interface is used in conjunction with the PROFILE attributes

• An attribute’s Interface is set to “Plugin-Interface” if the data for the same has to be retrieved by SPR Plugin

• Gx-Interface is used when the attribute needs to be shared from the GxSes-sion to any other session (currently only sharing to RxSession is supported)

Gx-Interface, Sh-Interface, LDAP-Interface, Local-DB-Interface, Plugin-Interface, Not-Appli-cable

Sh-Inter-face

S.No Parameter name



48


1.8 Attribute-Access-Mode

It defines Attribute-Access-Mode. It can be READ, WRITE, NOT_APPLICABLE and RESET parameters.READ: This parameter can be read only through provisioning.WRITE: This parameter can be updated through provisioning or PCS.

g Attribute-Access-Mode for PROFILE_SESSION attri-butes MUST be write

NOT_APPLICABLE: This must be used for SESSION and NSR attri-butes.

RESET: This parameter indicates which interface attribute should be set to zero once the request is pro-cessed (for INTERFACE). This is applicable for integer type attri-butes only which are used in Usage calculation. RESET is also used for attributes (PROFILE) that need to be reset when the Billing Period expires..WRITE_RESET: This parameter indicates which profile attribute should be set to zero once the billing period has expired.Refer to Datamodel Specification for CDM PCS document for READ, WRITE and RESET attri-butes.

g • The Attribute-Access-Mode for Billing Start Date is WRITE, and for Billing Duration and Bill Reset is READ.

• The Attribute-Access-Mode for Accumulated-Charge is WRITE.

string READ, WRITE, NOT_APPLICABLE, RESET

NOT_APPLICABLE

S.No Parameter name



49


• READ, WRITE and RESET are used for PROFILE attri-butes, and RESET and NOT_APPLICABLE are used for INTERFACE attributes.

• All parameters that require a SPR Read/Write/Reset must be mandatorily defined in the PCS_Attributes.xml.

1.9 Operation It specifies the mathematical oper-ation to be done to obtain the value of the attribute which will be accumulated/ added to the value present in the Database. It uses the calculator to update the value. That means +, -, *, /, no floating points, no spaces.

The Operation field in a SESSION or PROFILE parameter is used to indicate how this parameter is updated such as • Value assigned directly • Value assigned from an

existing Attribute • Value derived from an expres-

sion of existing AttributesFor example, $Attribute-Name1$+$Attribute-Name2$+$Attribute-Name3$+100.

string [_A-Za-z0-9\-]+ NA

1.10 Round-Off-Type

It specifies the Round Off Type. All attributes which have Round-Off-Type field is VOLUME that attri-bute is rounded. The Round-Off-Type value "TIME" is for future use.

string NO, VOLUME, TIME

NO

1.11 Reporting-Type

This field specifies how the reported data is used by plug-in for logging, generating statistics, or updating some database.

string NA NA

S.No Parameter name



50


1.12 Reporting-Name

This field specifies the name with which the attribute is reported.

g ReportingType and Reporting-Name are applicable only when Reporting plug-in is con-figured.

string NA NA

1.13 Reset-Con-dition

It specifies the condition on which the reset is done.

string NA NA

1.14 Reset-Value

This field specifies the attribute is reset based on the reset-value.

string NA NA

1.15 Copy-To The value before reset is copied to this field.

string NA NA

1.16 Send-To-SPR-Plugin

It specifies the name of the attri-bute as required by the plugin. This parameter is used to indicate if the “INTERFACE” parameter should be sent to the SPR-Plugin as a key for subscriber data retrieval.

string NA NA

1.17 Default-Value

Default-Value field is applicable for all attributes in Attributes.xml and it’s usage is optional. By default, PCS supports the following default values for the data types given below: • Integer default value is zero • Double default value is zero • Time default value is one • String default value is null (“”)

g For User-Agent-Type AVP, the supported values are 0 - NON_MOBILE_BROWSER, 1 - MOBILE_BROWSER. Since 0 is a defined value, it cannot be used as a default value. Hence for the User-Agent Attribute Value, the Default-Value must be over-ridden by any positive number which currently does not have a valid "meaning" as user-agent (for example, 255)

string NA NA

S.No Parameter name



51


2.2.16 Service configuration parametersDescribes the various service configuration parameter details.Gq interface:Following parameters are available in PCS_ServiceConfigParams.xml. These parame-ters require a process restart after modification.

Rx interface:Following parameters are available in PCS_ServiceConfigParams.xml. These parame-ters require a process restart after modification.

1.18 Required-For

Controls whether the attribute has to be sent to PRE or Reporting-Plugin REP or Both. If the attribute is just for PCS internal usage then it should be set to NONE.

Required-ForType

NONE/PRE / REP / PRE,REP

NONE

S.No Parameter name



S.No Parameter name


1 Watchdog_s This specifies the time interval for the Gq to send the Diameter watchdog request (DWR) message over the diameter connection. If it has a value 0 (zero) then Gq does not send the DWR over the diameter connection.


6

2 Connect-Retry-Timer-ms

The time interval (milliseconds) after that the PCS will try to re-connect to a network element when a connection has failed.


5000

3 Add-Gq-Authoriza-tion-Token

Indicates whether to send Gq authorization or not.


Table 23 Service configuration parameters: Gq interface

52


Gx interface:Following parameters are available in PCS_ServiceConfigParams.xml. These parame-ters require a process restart after modification.

Gy interface:Following parameters are available in PCS_ServiceConfigParams.xml. These parame-ters require a process restart after modification.

S.No Parameter name


1 Watchdog_s This specifies the time interval for the Rx to send the Diameter watchdog request (DWR) message over the diameter connection. If it has a value 0 (zero) then Gq does not send the DWR over the diameter connection.


6


The time interval (milliseconds) after that the PCS will try to re-connect to a network element when a connec-tion has failed.


5000

Table 24 Service configuration parameters: Rx interface

S.No Parameter name


1 Watchdog_s This specifies the time interval for the Gx to send the Diameter watchdog request (DWR) message over the diameter connection. If it has a value 0 (zero) then Gq does not send the DWR over the diameter connection.


6




5000

Table 25 Service configuration parameters: Gx interface

53


Sh interface:Following parameters are available in PCS_ServiceConfigParams.xml. These parame-ters require a process restart after modification.

Core:Following parameters are available in PCS_ServiceConfigParams.xml. These parame-ters require a process restart after modification except Case-Insensitive-Enabled parameter which is dynamically activated and doesnt require process restart.

Parameter name


Supported-GGSN-Release-Version

Specifies GGSN release version for Gy interface. string NA FISN32

Watchdog_s This specifies the time interval for the Gy to send the Diameter watchdog request (DWR) message over the diameter connection. If it has a value 0 (zero) then Gq does not send the DWR over the diameter connection.


6

Connect-Retry-Timer-ms



5000

Table 26 Service configuration parameters: Gy interface

S.No Parameter name


1 Watchdog_s This specifies the time interval for the Sh to send the Diameter watchdog request (DWR) message over the diameter connection. If it has a value 0 (zero) then Gq does not send the DWR over the diameter connection.


6

Table 27 Service configuration parameters: Sh interface

54


Parameter name


Path-Name-Of-Counter-File-Dir

It specifies the full path of the directory where the performance counter files are located. By default it is the name of the home directory of the PMftp user account and it is to used to retrieve these files using ftp.

string NA /export/home/PMftp

Dump-Counters-To-Files

It specifies whether PCS gener-ates performance counter files. The format is as specified in TS 32401.


Passive-Sip-Forking-Support

If it is set to true then PCS supports SIP forking else it does not.


Time-Interval-To-Dump-CPU-Counters

Time-Interval-To-Dump-CPU-Counters

integer Integer greater than or equal to 1

15

Time-Interval-To-Dump-Counters_s

It specifies the time difference between generating subsequent performance counter files. The time is set in seconds as required by TS 32401 section 5.4.1.4 (granularity period), additional value 60. This parameter gives the period of time the period specific performance counters refers to.

g This parameter can be used even if no performance counter files are generated.


900

Do-Overload-Control

Enables or disables the overload control.


SMS-Notifica-tion-Enabled

Enables or disables the SMS Notification.


Use-Policy-Rule-Engine-Enabled

It specifies the PRE enabled status.

g Value false is not supported for CPCS scenario.


Table 28 Service configuration parameters: core

55


Subscriber-Notification-Plugin-Enabled

Enables or disables Subscriber-Notification-Plugin feature.


Volume-Reset-Enabled

Enables or disables the volume reset.


Terminal-Identifier

Terminal Identifier contains list of comma seperated Subscription Identifiers with the first value having the highest priority.

string IMSI, MSISDN, SIPURI or FRAMEDIP

IMSI

Case-Insensi-tive-Enabled

It specifies the Case-Insensitive is enabled.


RSYNC-Retry-Limit

This parameter is used to config-ure the rsync failure attempts.

Integer 1 to 3 1

RSYNC-Retry-DelayTimer_s

This parameter is used to config-ure the rsync delay timer.

Integer 0 to 2147483647 1

GroupCoun-ters-Enabled

Feature flag used to enable or disable the Group Counters feature

boolean true, false FALSE

UnifiedSPR-Enabled

Feature flag used to enable or disable the Unified SPR Usage


Billing-Cycle-Reset

Consists of the below mentioned tags

Midnight-Billing-Reset

If the value is set to true, then billing reset will happen in the mid night

boolean true, false TRUE

Read-As-UTC-Time

If value is set to false, time read from SPR is considered as local time


MultipleIPCan Consists of below mentioned tags

Enabled This flag is used to enable or disable support of Multiple-IpCan session


Parameter name


Table 28 Service configuration parameters: core (Cont.)

56


Common:Following parameters are available in PCS_ServiceConfigParams.xml. These parame-ters require a process restart after modification.

Overload:Depending on the PCS configuration, the operator can configure the overload parame-ters for different interfaces in the network. The parameters can be varied based on the enabled interface and traffic model. The following table shows the default values and ranges for each interface. The values indicated in the table are applicable only when a single interface is enabledFollowing parameters are available in PCS_ServiceConfigParams.xml. These parame-ters require a process restart after modification.

Identifier This parameter should be config-ured with identifier to uniquely identify IpCan session.

string "IMSI_FRAMEDIP_PDNID","MSISDN_FRAMEDIP_PDNID","SIPURI_FRAMEDIP_PDNID","IMSI_FRAMEDIP","IMSI_PDNID","MSISDN_FRAMEDIP","MSISDN_PDNID","SIPURI_FRAMEDIP","SIPURI_PDNID"

IMSI_FRAMEDIP_PDNID

DIA-Result-Code-Lock-Failure

This parameter is used to config-ure the result code with which messages are rejected if lock failures and queing of messages is set to false

Unsigned Integer

1 to 4294967295 4002

DIA-Lock-Failure-Result

This parameter is used to config-ure the result type to be send for rejected messages in case of lock failure.

string NORMAL, EXPER-IMENTAL

NORMAL

Parameter name


Table 28 Service configuration parameters: core (Cont.)

Parameter name


MNC-Length It specifies the MNC lengthAttribute. It can be either two or three

integer 2 or 3 2

Table 29 Service configuration parameters: common

57


g The parameters for each individual interface cannot be set to more than the default value when SPR and PRE are enabled. For the feature "Policy Evaluation without SPR", the default Max-Msg-Rate for Gx, Gy and Radius can be increased to 4000.

Ia-Interface

Parameter name


Gq-Max-Msg-Rate

It specifies the Gq’s maximum message rate.

Not support in the current version, appli-cable for SPDF scenario only.


7000

Ia-Max-Msg-Rate

It specified the Ia’s maximum message rate. It is a dummy parameter.Not support in the current version, appli-cable for SPDF scenario only.


7000

Rx-Max-Msg-Rate

It specifies the Rx’s maximum message rate.

integer 1 to 20000 3000

Gx-Max-Msg-Rate

It specifies the Gx’s maximum message rate.

integer 1 to 20000 5000

Gy-Max-Msg-Rate

It specifies the Gy’s maximum message rate.Not support in the current version, appli-cable for CPCS scenario only.


4000

Ra-Max-Msg-Rate

It specifies the Ra’s maximum message rate.Not support in the current version, appli-cable for CPCS scenario only.


3000

Soap-Max-Msg-Rate

It specifies the Soap’s maximum message rate.

integer 0 to 200 200

Table 30 Service configuration parameters: overload

Parameter name


DSCP-Marking-Enabled

DSCP-Marking-Enabled boolean true,false TRUE

DSCP DSCP string "10","12","14","18","20","22,"26","28","30","34","36","38","46"

46

Table 31 Service configuration parameters: Ia interface

58


Dia-InterfaceFollowing parameters are available in PCS_ServiceConfigParams.xml. These parame-ters require a process restart after modification.

For all above interfaces,

Multiplication factor = Max-Msg-Rate / Max-Iterations.

g This is application for Overload parameters calculation.

See Table 33.

g If PCS is configured as a Gy-Proxy then the multiplication factor for Gy interface is 4.

If more than one interface is configured in PCS,Total Message Rate = Minimum of enabled interfaces.

Parameter name


Watchdog_s This specifies the time interval for the DIA-Interface to send the Diameter watchdog request (DWR) message over the diameter connection. If it has a value 0 (zero) then DIA-Interface does not send the DWR over the diameter connection.


6

Connect-Retry-Timer_ms

The time interval (milliseconds) after that the PCS will try to reconnect to a network element when a connection has failed


5000

IPv6Prefix-CutOff-Length

This is used by PCS to extract the IPv6Prefix from 128-bit full address received in Rx-AAR which will be required for session binding

integer 0 to 128 64

Table 32 Service configuration parameters: Dia interface

Interface Multiplication factor

Rq 2

Gq 5

E4 2

Rx 2

Gx 2

Gy 2

Ra 2

Table 33 Interface-Multiplication factor

Total Message Rate = Min (Enabled Interfaces)

= Min(Gx-Max-Msg-Rate, Gq-Max-Msg-Rate)

59


For example, if Gx and Gq are configured,The Total Message Rate should be divided between the enabled interfaces (Gx, Gq) depending on the traffic model. For example, If the traffic model is Gx:Gq = 2:1 then Gx-Max-Msg-Rate = 2000 and Gq-Max-Msg-Rate = 1000.

2.2.17 Subscriber parametersFollowing are the subscriber parameter listed in the schema file and are of type Gq or Rx interface type, Gx-Interface Type.

g Internal-DB as SPR is not supported.

= (3000, 4000)

= 3000

S.No Parameter name


1 Add Sub-scriber

This section gives the list of elements that are to be added to the existing subscribers.

Add-Sub-scriber-sType

NA NA

1.1 Subscriber-Data

Contains subscriber related infor-mation like subscriber id, billing plan, pricing plan, category, sub-scriber plan, charging rule, SGSNs and so on.

Subscrib-erData-Type

NA NA

1.1.1 Subscriber-Id

Used for specifying the identifier for the subscriber.

integer NA 10000003

1.1.2 Billing-Plan Used for specifying the billing plan for the subscriber.

string NA prepaid

1.1.3 Pricing-Plan Used for specifying the pricing plan for the subscriber.

string NA value

1.1.4 Category Used for specifying the category for the subscriber.

string NA TierA

1.1.5 Subscriber-Plan

It specifies the charging type for the subscriber.

string NA gold

1.1.6 Charging-Rule

It specifies the charging rule for the subscriber.

integer NA 3

1.1.7 Allowed-Services

It specifies the allowed service for the subscriber.

integer NA 1

1.1.8 Accumulat-edCharge

This specifies the accumulated charge for the subscriber.

integer NA 0

1.1.9 Consump-tionLimit

This specifies the consumption limit for the subscriber.

integer NA 1000

Table 34 Subscriber data parameters

60


1.1.10 Notification-Threshold

This specifies the notification threshold for the subscriber.

integer NA 60

1.1.11 TotalThresholdQuota

This specifies the total threshold quota for the subscriber

integer NA 200000

1.1.12 Uplink-Threshold-Quota

This specifies the uplink threshold quota for the subscriber.

integer NA 100000

1.1.13 DownLink-Threshold-Quota

This specifies the downlink thresh-old quota for the subscriber.

integer NA 100000

1.1.14 UserNotifi-cationType

This specifies the UserNotification-Type for the subscriber. There are five options. sms(only sms will be sent),email (only email will be sent ), redirection ( only redirection will be done ), smsandredirection(both sms and redirection can be done), none(none of the notifications are provided to the subscriber).

string sms, email, redirec-tion, smsandredi-rection, none

none

1.1.15 HomeLoca-tion

This specifies the home location for the subscriber.

string “ “

1.1.16 BillingStart-Date

This specifies the billing start date for the subscriber. Format of date is yyyy-mm-dd-HH:MM:SS and date of month can be from 1 to 31.

g If the billing period is date and duration, then HH:MM:SS is optional..

string NA 2009-01-01

S.No Parameter name


Table 34 Subscriber data parameters (Cont.)

61


1.1.10 Notification-Threshold

This specifies the notification threshold for the subscriber.

integer NA 60

1.1.11 TotalThresholdQuota

This specifies the total threshold quota for the subscriber

integer NA 200000

1.1.12 Uplink-Threshold-Quota

This specifies the uplink threshold quota for the subscriber.

integer NA 100000

1.1.13 DownLink-Threshold-Quota

This specifies the downlink thresh-old quota for the subscriber.

integer NA 100000

1.1.14 UserNotifi-cationType

This specifies the UserNotification-Type for the subscriber. There are five options. sms(only sms will be sent),email (only email will be sent ), redirection ( only redirection will be done ), smsandredirection(both sms and redirection can be done), none(none of the notifications are provided to the subscriber).

string sms, email, redirec-tion, smsandredi-rection, none

none

1.1.15 HomeLoca-tion

This specifies the home location for the subscriber.

string “ “

1.1.16 BillingStart-Date


g If the billing period is date and duration, then HH:MM:SS is optional..


S.No Parameter name



62


1.1.17 BillingPe-riod

It specifies the billing period or duration for the subscriber. Duration is set in days.If the BillResetType is duration, then this specifies the billing period or duration (in number of days) for the subscriber.

If the BillResetType is date then this field represents the date on which reset is effected every month.If the BillResetType is hours, then this field represents the number of hours after which a reset occurs.If the BillResetType is minutes, then this field represents the number of minutes after which a reset occurs(taken as billing period).

integer 1 to 31 30

1.1.18 Uplink-Usage

It specifies the upload usage by subscriber

integer NA 0

1.1.19 Downlink-Usage

It specifies the download usage by subscriber

integer NA 0

1.1.20 Total-Usage It specifies the total usage by sub-scriber

integer NA 0

1.1.21 Time-Usage It specifies the usage in time for the subscriber. It uses the format Hrs:Mins:Secs.

integer NA 0

1.1.22 BillReset-Type

It specifies the billing reset type for the subscriber. It can be duration, date, hours and minutes.Duration: Number of days after which a reset occurs(taken as billing period).Date: Particular date on which a reset occurs (day of month taken from billing start date).

Hours: Number of hours after which a reset occurs(taken as billing period).Minutes: Number of minutes after which a reset occurs(taken as billing period).

string duration, date, hours, minutes

duration

S.No Parameter name



63


1.1.23 First-Use_Roaming

Enables or disables the First Use Roaming.


1.1.24 First-Use-Home

Enables or disables the First Use Home.


1.1.25 pcsSub-scriberAc-tionStatus

This specifies the usage limit of the subscriber.

If this value is zero means volume usage is within the limit.

If this value is one means sub-scriber reaches usage limit.

integer 0, 1 0

1.1.26 Rollover-Enabled

The attribute indicates if the rollover for the subscriberInfo is enabled or not. PCS supports simple monthly rollover of quota and the flag indi-cates if this is applicable for the subscriberInfo.


1.1.27 Redirection-Indication

The attribute indicates if the redirec-tion notification has been sent to the user. TRUE: Redirection Notifica-tion sent, FALSE: Redirection Noti-fication not sent


1.1.28 SMS-Notifi-cations-Msisdn

MSISDN of device for SMS notifica-tions. This is a 10...15 digit decimal number.

Integer NA NA

1.2 List-of-home-SGSNs

It contains a list of home SGSNs. List-of-home-SGSNs-Type

NA NA

1.2.1 IP-Address-Prefix

It provides the SGSN IP Address. IP-Address-Prefix-Type

NA NA

1.2.1.a Address It represents IP Address of V4 or V6.

IPAddress-Type

IPv4, IPv6 10.0.0.0

1.2.1.b Mask It represents mask for SGSN. MaskType NA 8

1.3 Table-of-Services

It specifies the service supported by the subscriber.

Table-of-Services-Type

NA NA

1.3.1 ServiceInfo It provides list of services that is applicable for the subscriber.

Services-Info-Type

NA NA

S.No Parameter name



64


1.3.1.a Service-Id It specifies the service ID. integer NA 1

1.3.1.b Service-Name

It is the name of service used. string NA skype

1.3.1.c Service-Enabled

It is a boolean value which states the status.


1.3.1.d Service-BillingStart-Date


g If the billing period is date and duration, then HH:MM:SS is optional.


1.3.1.e Service-BillingPe-riod

It specifies the billing period or duration for the subscriber. Duration is set in days.If the Service-BillResetType is duration, then this specifies the billing period or duration (in number of days) for the subscriber.If the Service-BillReset is date then this field represents the date on which reset is effected every month. If the Service-BillReset is hours, then this field represents the number of hours after which a reset occurs.If the Service-BillReset is minutes, then this field represents the number of minutes after which a reset occurs(taken as billing period).

integer 1 to 31 30

S.No Parameter name



65


1.3.1.f Service-Bill-ResetType

It specifies the billing reset for the subscriber. It can be duration, date, hours and minutes.Duration: Number of days after which a reset occurs(taken as billing period).Date: Particular date on which a reset occurs (day of month taken from billing start date).

Hours: Number of hours after which a reset occurs(taken as billing period).Minutes: Number of minutes after which a reset occurs(taken as billing period).

string duration, date, hours, minutes

duration

1.3.1.g Service-Accumulat-edCharge

It specifies the accumulated charge.

integer NA 0

1.3.1.h Service-Uplink-Usage

It specifies the total upload usage. integer NA 0

1.3.1.i Service-Downlink-Usage

It specifies the total download usage.

integer NA 0

1.3.1.j Service-Total-Usage

It specifies the total service usage. integer NA 0

1.3.1.k Service-Time-Usage

It specifies the total time usage, time format is hrs:mins:secs

integer NA 0.0.0

1.3.1.l Service-Total-Threshold-Quota

It specifies the total threshold usage.

integer NA 0

1.3.1.m Service-Uplink-Threshold-Quota

It specifies the uplink threshold usage.

integer NA 0

1.3.1.n Service-Downlink-Threshold-Quota

It specifies the downlink threshold usage.

integer NA 0

S.No Parameter name



66


1.3.1.o Service-Node-Id

It specifies the service node id. integer NA 0

1.3.1.p Service-Element-Cyclic

The attribute indicates the servi-ceElement to be cyclic or not. The attribute is used by PCS to decide if the billing reset for the serviceEle-ment be cyclic or one-time.


1.3.1.q Service-Rollover-Enabled

The attribute indicates if the rollover for the serviceElement is enabled or not. PCS supports simple monthly rollover of quota and the flag indi-cates if this is applicable for the service.


1.3.1.r Service-Action-Status

The attribute indicates the action taken based on the policy decision for the Service. The attribute is not an enumeration and can hold any value. Values below are only examples - 0 : No Action, 1 : indi-cates volume exceeded threshold for that service

String NA NA

1.3.1.s Service-Thresh-Future-Quota

This attributes contains the volume available with subscriber for partic-ular service that is applicable from next billing cycle. Default value set to Zero. Both PCS and PGW should be able to modify the attribute.

Integer NA 0

1.4 Table-of-Packages

It specifies the packages supported for subscriber

Table-of-Packages Type

NA NA

1.4.1 Packages-Info

It provides list of packages for Turbo Boost

Packages-Info Type

NA NA

1.4.1.a PcsSub-PackId

It specifies the package Id and it must be unique within a subscriber data

integer integer value is 1 to 2^32-1

1

1.4.1.b PcsSub-PackStatus

It specifies whether the package is active or inactive. True means active and false means inactive.


S.No Parameter name



67


g 1. An operator can also modify the existing subscriber information .2. Allowed-Services and Charging-Rule are deprecated fields in internal database.3. DPI_CISCO and DPI_SANDVINE peer-types configurations are deprecated and will

not be available in future releases

1.4.1.c PcsSub-PackStart-DateTime

It specifies the start date and time of the package. The format of the date and time is YYYY-MM-DDThh:mm:ss.nnn.

gYYYY means Year, MM means Month, D means Date, T means the date and time value separa-tor and is required by policy rule engine, hh means Hour (0-23), mm means Minutes, ss means Seconds, and nnn means time in milliseconds.

string NA system date and time

1.4.1.d PcsCy-cleNumber

The attribute contains cycle number for the subscriber

Integer NA 0

1.4.1.e PcsCam-paignNum-ber

The attribute contains campaign -id for the subscriber

Integer NA 0

1.4.1.f PcsSub-PackUsage

This attribute contains the volume used with package in bytes.

Integer NA 0

1.4.1.g PcsSub-PackUser-NotificationURL

Redirection URL to which user had to be redirected when the package expires.

Integer NA 0

1.4.1.h PcsSub-Pack-QuotaThreshold

This attribute contains the volume available with package in bytes

Integer NA 0

3 Delete-Sub-scribers

It lists all the subscribers that are to be deleted from the existing sub-scribers.

Delete-Subscrib-ersType

NA NA

3.1 Subscriber-To-Delete

This section gives the Subscriber to be deleted.

Sub-scriber-To-Delete-Type

NA NA

3.1.a Subscriber-Id

It specifies the Identifier for the sub-scriber for the deleted.

integer NA 10000003

S.No Parameter name



68


2.2.18 QoS Selection parametersThis section describes the parameters that are used in the PCS_QosAndChargingSelection XML file. Operator defined e.g media or codec based QoS profiles for QoS authorization (VoLTE feature) are configured in PCS_QosAndChargingSelection XML file.

Parameter name

Parent tag Description Type Value range Default

Qos-Selec-tion-Table

This is the main tag within which all the parameters corresponding to Qos selection are to be configured for CPCS

Qos-Selec-tion

Qos-Selec-tion-Table

Under this, various Qos profiles can be added. Each Qos profile can be either Media based, Codec based or AFID based.

Qos-Selec-tion-Name

Qos-Selec-tion

Name of the Qos profile. Contains a name which is expected in the incoming message over Rx interface

String [0-9a-zA-Z_/.\-]+

Audio

Qos-Selec-tion-Type

Qos-Selec-tion

Indiactes a Qos Selection Type based on which the Qos-Information is composed in CCA or RAR

Enum MEDIA_TYPE or CODEC_TYPE or AFID_TYPE

MEDIA_TYPE

Monitoring-Key

Qos-Selec-tion

Monitors QoS selection String [0-9a-zA-Z_/.\-]+

monitoring-key

List-of-BW-Profile-Names

Qos-Selec-tion

Contains a list of BW profiles on which the BandWidth-Selection Algorithm will be applied from Qos-Selection obligation

BW-Profile List-of-BW-Profile-Names

Contains a BW profile name

BW-Profile-Name

BW-Profile Name should be one among those for which BW profiles are present within "List-Of-BW-Profiles"


*

List-of-ARP-Profile-Names

Qos-Selec-tion

Contains a list of ARP profiles on which the ARP-Selection Algorithm will be applied from Qos-Selection obligation

ARP-Profile List-of-ARP-Profile-Names

Contains a ARP profile name

Table 35 QoS Selection parameters

69


ARP-Profile-Name

ARP-Profile Name should be one among those for which ARP profiles are present within "List-Of-ARP-Profiles"


*

List-of-QCI Qos-Selec-tion

Contains a list of QCI values ranging from 0 through 255 on which the QCI-Selection Algorithm will be applied from Qos-Selection obligation

QCI List-of-QCI Contains QCI value

QCI-Value QCI Indicates the valus of QUI String 0-255 0

List-of-BW-Profiles

Contains profiles in which BW specific values are configured like Maximum-UL/DL, Guaranteed UL-D, APN-AMBR UL/DL

BW-Profile-Name

List-of-BW-Profiles


qos2

Max-Band-width-UL

List-of-BW-Profiles

Indicates the authorized maximum bitrate for the uplink component of the service data flow.'Maximum bitrate' can be used for enforcement of the maximum bit rate that the (Service Data Flow)SDF may consume

String -|[0-9]+ -

Max-Band-width-DL

List-of-BW-Profiles

Indicates the authorized maximum bitrate for the downlink component of the service data flow.'Maximum bitrate' can be used for enforcement of the maximum bit rate that the (Service Data Flow)SDF may consume

String -|[0-9]+ -

Guaran-teed-Band-width-UL

List-of-BW-Profiles

Indicates the authorized guaranteed bitrate for the uplink component of the service data flow.The 'Guaranteed bitrate' is used by the PCEF to deter-mine resource allocation

String -|[0-9]+ -

Guaran-teed-Band-width-DL

List-of-BW-Profiles

Indicates the authorized guaranteed bitrate for the downlink component of the service data flow.The 'Guaranteed bitrate' is used by the PCEF to deter-mine resource allocation

String -|[0-9]+ -

APN-AMBR-UL

List-of-BW-Profiles

Denotes the uplink Aggregate Maximum Bit Rate of traffic per group of bearers

String -|[0-9]+ -

Parameter name


Table 35 QoS Selection parameters (Cont.)

70


APN-AMBR-DL

List-of-BW-Profiles

Denotes the downlink Aggregate Maximum Bit Rate of traffic per group of bearers

String -|[0-9]+ -

List-of-ARP-Profiles

Contains list of ARP profiles each con-sisting of Priority, pre-emption capabil-ity pre-emption vulnerability

ARP-Profile-Name


Name should be one among those for which ARP profiles are present within "List-Of-ARP-Profiles"


Arp-profile1

ARP-Value List-of-ARP-Profiles

Indicates the priority level which defines the relative importance of a resource request.This allows deciding whether a bearer establishment or modification request can be accepted or needs to be rejected in case of resource limitations

String 1-15 (1 being highest)

Pre-Emption-Capability


Defines whether a service data flow can get resources that were already assigned to another service data flow with a lower priority level

String 1(yes) or 0(no)

-

Pre-Emption-Vulnerability


Defines whether a service data flow can lose the resources assigned to it in order to admit a service data flow with higher priority level

String 1(yes) or 0(no)

-

Parameter name


Table 35 QoS Selection parameters (Cont.)

71


2.3 Restrictions for PCM objectsThe following are the restrictions that need to be followed while creating and editing of PCM objects:1. The PCS Host names should only have alpha-numeric characters. No special char-

acters are allowed except for underscore "_". In the PCS View no special characters are allowed for IP Address of a PCS Host.

2. No special characters are allowed for IP Addresses while creating a new or editing a PCS_HostSpecificConfigParams.xml file.

3. The PCS Group names should only have alpha-numeric characters. No special characters are allowed except for underscore "_".

4. For PCS Manager the PCS Group is restricted to contain only one PCS Host. 5. The PCS Project names should only have alpha-numeric characters. No special

characters are allowed except for underscore "_".6. The Access Rule file names should start with “PCS_AccessRule”.7. If a file is loaded in the PCM Editor you should not click “Create it” in the “Next Steps”

window.8. If the type of the PCS Host is null, then the PCS Host cannot be assigned to a PCS

Group.9. It is recommended to create a already started PCS.10. It takes long time to create PCS Host if the IP Address of the PCS Host is invalid. It

is recommended to enter valid IP Address for the PCS Host.11. A Project can be accessed by a single user at a time.12. Any XML file (PCS_HostSpecificConfigParams file, PCS_GeneralConfigParams

file, PCS_QoSAndChargingSelection file and PCS_AccessRules file) should be saved after modification.

13. Either the IP-Address or the Host-Name XML tag must be present in the appropriate sections of an XML file. However, if both the tags are missing, the PCM Editor will not give an error message on validation of either the Project or an XML file. This error will be captured by the PCS on activation of the Project or an XML file.

14. Import file does not check for the project type of the file to be imported but it validates

the file against the corresponding schema before importing.

72

Reference Guide Counter Description

3 Counter Description

3.1 IntroductionMonitoring the performance data of the network elements (NEs) in a network provides the operator with important information about the system. PCS provides this information in the form of performance counters. Counter data contains information about system performance like call usage pattern, number of requests denied, reason for denial and so on. This helps the network operator in dimensioning the network.

3.1.1 Types of countersAccording to the PCS architecture, PCS generates two types of counter data. They are categorized into: • Internal counter

Used to count the number of messages sent or received for the transactions between the policy distributor and the peer network elements or policy servers. For details see 4 Internal counters.

• Performance counterFor complete list of performance counters see section 5 Performance counters.

3.1.2 Types of PCS Performance CountersThe following types of PCS performance counters are used: • gauge

current number, indicates the number of currently existing sessions; is incremented and decremented; is not reset (except on process startup).

• eterSum (“eternal” sum)number, indicates the number of received messages since PCS process start (in an advanced PCS version); is incremented but not decremented; is not reset (except manually by operator).

• tempSum (temporary sum)number, indicates the number of received messages during current period, that is, since last dump of counters to file; is incremented but not decremented; is reset onthat dump.

• eterMax (“eternal” maximum)max number, indicates the number of simultaneously existing sessions since PCSprocess start (in an advanced PCS version); is incremented butnot decre-mented; is not reset (except manually by operator).

• eterMax per periodmax number, indicates the number of received messages, per period since PCS process start (in an advanced PCS version); is incremented butnot decremented; is not reset (except manually by operator).

• tempMax (temporary maximum)max number, indicates the number of simultane-ously existing sessions during current period, that is, since last dump of counters to file; is incremented but not decremented; is reset on that dump.

3.1.3 Viewing countersPCS provides the following interfaces to view counters:

71

Reference GuideCounter Description

• NetAct GUI

PCS, on a regular basis allows the dumping of counter files through file transfer protocol (FTP) for further post processing.

Refer to the respective interface documents for instructions on how to check and con-figure counters.

3.1.4 Guideline to check counter dataOperator should keep the following points in mind while checking for counter data:

• PCS periodically updates the counter values to file. The duration after which the counter values are dumped to file, is specified in the parameter timeIntervalToDumpCounters_s. By default the counter values are dumped to file every 900 seconds. Operator can configure this parameter through PCM GUI. The parameter is present in PCS_ServiceConfigParams.xml file.

• PCS allows the operator to view counter values in the following way. • File dumping - here, PCS dumps counter values to file periodically. Counter

values the operator gets, is the value at the time of last dump. • Valid messages

A received message is counted as valid message if and only if it has successfully passed the validity verifications in PCS. Validity verifications check for the complete-ness and correctness of the message.

3.2 Key performance indicatorsMonitoring the performance data and the load of the elements in the network provides the operator with important information about the system. It helps the network operator to detect and eliminate bottlenecks and vulnerable points. Thus, it helps to maintain and improve the performance of the system and protects it from overload.

In NetAct, Reporter is a performance management and reporting solution, using which you can perform real-time evaluation of performance data.

Key performance indicator (KPI) definition is used to define indicators to monitor the per-formance of the system. The KPI counters are defined by combining counters through a definition that contains the counter name, the expression how to calculate the counters (total sum, average sum, max, min) and the list of network elements for which the KPI counter is to be calculated.

g Performance objects are counters that register performance data in the different network elements (NEs). Each time the event occurs and each time you start to measure an event, the counter is incremented. Performance objects (PO) are in charge of regis-tering performance data and this data is the base for the calculation of a KPI.

In NetAct, the performance monitoring feature is accessed by selecting “Reporting j Reporter”.

3.2.1 Administering key performance indicatorsThe basic POs defined by the Network Element Manager do not always meet all require-ments. Therefore, you can use the KPI editor to define KPI ><. KPIs are calculated by using algorithms based on basic performance counters and allow you to customize the performance views and define performance counters distributed over NEs. A custom-

72


ized KPI can be used as any basic PO. A KPI can consist of the counters of one network element and/or of different network elements. The KPI expression contains arithmetic operators, such as add (+), subtract (-), multiply (*), divide (/), numbers (0-9), decimal points (.) and basic functions, such as minimum (MIN), maximum (MAX), average (AVG), and sum (SUM). In addition to creating KPI you can also display and modify existing KPIs. An existing KPI cannot be used in creating another KPI.

3.2.2 Creating KPIYou can customize new POs from the basic POs and create new KPIs using the KPI editor.

3.2.3 Examples of KPIsThe basic KPIs, explained in this section, ensure an effective monitoring of the perfor-mance behavior. KPIs can be defined for all network elements managed by the Network Element Managers. For using these KPIs, the operator must edit the formulas with the help of KPI editor.

To make these measurements there are defined base counters that monitor at the NE PCS. The Network Element Manager is the central point, where all the KPIs are visible to the customer. The network element manager fetches all input counters and integrates those in the KPI equation. KPIs are then visualized in the Network Element Manager GUI. All currently available KPIs are NE-related KPIs. NE-related KPIs monitor the behavior of the subscribers. The KPIs can be created at the Network Element Manager using the counters available there. For more information on how to create a KPI see the section 3.2.2 Creating KPI.

g Further KPIs can be defined on a project specific basis.

3.2.3.1 Valid Gq messages received rate

DescriptionValid Gq message received rate KPI measures the success rate of Gq messaging between AF and PCS with respect to the number of valid and invalid Gq messages received within the last calculation interval.

73


Figure 2 Call Flow for the KPI valid Gq messages received rate

Create KPI equationValid Gq messages received rate = 100* Valid Gq messages received in last period / (Valid Gq messages received in last period + Invalid Gq messages received in last period ) [%]

To create the Valid Gq messages received rate KPI, you need the following counters: • Invalid Gq Messages Received in Last Period

Counts the number of invalid Gq messages received by the PCS instance in the last calculation interval. This counter is incremented at the instance whenever a illegiti-mate message is received by the PCS interface.

• Valid Gq Messages Received in Last PeriodCounts the number of valid Gq messages received by the PCS instance in the last calculation. This counter is incremented at the instance whenever a legitimate message is received by the PCS interface.

3.2.3.2 Invalid Gq messages received rate

DescriptionInvalid Gq message received rate KPI measures the failure rate of Gq messaging between AF and PCS with respect to the number of valid and invalid Gq messages received within the last calculation interval.

74


Figure 3 Call Flow for the KPI invalid Gq messages received rate

Create KPI equationInalid Gq messages received rate = 100* Invalid Gq messages received in last period / (Valid Gq messages received in last period + Invalid Gq messages received in last period ) [%]

To create the Invalid Gq messages received rate KPI, you need the following counters: • Invalid Gq Messages Received in Last Period

Counts the number of invalid Gq messages received by the PCS instance in the last calculation interval. This counter is incremented at the instance whenever a illegiti-mate message is received by the PCS interface.

• Valid Gq Messages Received in Last PeriodCounts the number of valid Gq messages received by the PCS instance in the last calculation. This counter is incremented at the instance whenever a legitimate message is received by the PCS interface.

3.2.3.3 Valid Ia messages received rate

DescriptionValid Ia message received rate KPI measures the success rate of Ia messaging between PCS and BGF with respect to the number of valid and invalid Ia messages received within the last calculation interval.

75


Figure 4 Call Flow for the KPI valid Ia messages received rate

Create KPI equationValid Ia messages received rate = 100* Valid Ia messages received in last period / (Valid Ia messages received in last period + Invalid Ia messages received in last period ) [%]To create the Valid Ia messages received rate KPI, you need the following counters:

• Invalid Ia Messages Received in Last PeriodCounts the number of valid Ia messages received by the PCS instance in the last calculation interval. This counter is incremented at the instance whenever a illegiti-mate message is received by the PCS interface.

• Valid Ia Messages Received in Last PeriodCounts the number of invalid Ia messages received by the PCS instance in the last calculation interval. This counter is incremented at the instance whenever a legiti-mate message is received by the PCS interface.

3.2.3.4 Invalid Ia messages received rate

DescriptionInvalid Ia message received rate KPI measures the failure rate of Ia messaging between PCS and BGF with respect to the number of valid and invalid Ia messages received within the last calculation interval.

76


Figure 5 Call Flow for the KPI invalid Ia messages received rate

Create KPI equationInvalid Ia messages received rate = 100* Invalid Ia messages received in last period / (Valid Ia messages received in last period + Invalid Ia messages received in last period ) [%]To create the Invalid Ia messages received rate KPI, you need the following counters:

• Invalid Ia Messages Received in Last PeriodCounts the number of valid Ia messages received by the PCS instance in the last calculation interval. This counter is incremented at the instance whenever a illegiti-mate message is received by the PCS interface.

• Valid Ia Messages Received in Last PeriodCounts the number of invalid Ia messages received by the PCS instance in the last calculation interval. This counter is incremented at the instance whenever a legiti-mate message is received by the PCS interface.

3.2.3.5 Rate of messages denied by the Policy Rule Engine

DescriptionRate of messages denied by the Policy Rule Engine KPI gives the rate of the denied policies in a Call flow.

77


Figure 6 Call Flow for KPI rate of messages denied by policy rule engine

Create KPI equationRate of messages denied by the Policy Rule Engine = 100* Messages permitted by Policy Rule Engine in last period / (Messages permitted by Policy Rule Engine in last period + Messages denied by Policy Rule Engine in last period ) [%]

To create this KPI, you need the following counters: • Messages Denied by Policy Rule Engine in Last Period

Counts the number of messages denied by access policy rule engine in PCS instance in the last calculation interval. It is incremented at the instance whenever a Deny is forced upon the policy evaluation by the PRE for a call flow.

• Messages Permitted by Policy Rule Engine in Last PeriodCounts the number of messages permitted by access policy rule engine in PCS instance in the last calculation interval. It is incremented at the instance whenever a Permit is granted upon the policy evaluation by the PRE for a call flow.

3.2.3.6 Rate of messages permitted by the Policy Rule Engine

DescriptionRate of messages permitted by the Policy Rule Engine KPI gives the success rate of the permitted policies in a Call flow.

78


Figure 7 Call Flow for KPI rate of messages permitted by policy rule engine

Create KPI equationRate of messages permitted by the Policy Rule Engine = 100* messages permitted by Policy Rule Engine in last period / (messages permitted by Policy Rule Engine in last period + messages denied by Policy Rule Engine in last period ) [%]

To create this KPI, you need the following counters: • Messages Permitted by Policy Rule Engine in Last Period

Counts the number of messages permitted by access policy rule engine in PCS instance in the last calculation interval. It is incremented at the instance whenever a Permit is granted upon the policy evaluation by the PRE for a call flow.

• Messages Denied by Policy Rule Engine in Last PeriodCounts the number of messages denied by access policy rule engine in PCS instance in the last calculation interval. It is incremented at the instance whenever a Deny is forced upon the policy evaluation by the PRE for a call flow.

3.2.3.7 Ratio of rejected Gq messages due to overload

DescriptionRatio of rejected Gq messages due to overload KPI measures the rejection rate of Gq messaging between PCS and AF with respect to the number of overload and valid Gq messages received for the last calculation interval.

79


Figure 8 Call Flow for KPI rejected Gq messages due to overload

Create KPI equationRatio of rejected Gq messages due to overload = 100* Rejecting overload Gq messages sent in last period / (Valid Gq messages received in last period) [%]To create this KPI, you need the following counters:

• Rejecting Overload Gx Messages Ever SentCounts the number of rejecting Gx messages sent by the PCS instance for PCS overload protection since system start. It is incremented at the instance whenever a a message is rejected due to overload in the system.

• Valid Gq Messages Received in Last PeriodCounts the number of valid Gq messages received by the PCS instance in the last calculation. This counter is incremented at the instance whenever a illegitimate (syn-tactically and semantically NOT according to protocol specification) message is received by the PCS interface.

3.3 Internal countersThis type of counters are specific to the policy distributor. It depends on the peer or policy server connected to the policy distributor. These counters are pre-defined and cannot change without a software update.The naming convention for an internal counter is as follows:<FE_NAME or PEER NAME>/<INTERFACE_TYPE>/<COMMANDCODE><COMMANDTYPE>

Where,

• FENAME or PEERNAMEIs the name name of the policy server or the peer network element connected the the policy distributor.

• INTERFACE_TYPEGives the interface type used to to connect to the peer element. Possible values for interface type are:– GQ - Gq interface– GX - Gx interface

80


– GY - Gy interface– RX - Rx interface– RA - Radius interface

• COMMANDCODEIndicates the message type. Possible values are:– CC - Credit Control– RA - Re Authorization– AS - Abort Session– ST - Session Termination– AA - Authentication Authorization– ACR - Radius accounting request– ACA - Radius accounting response– CAR - Radius change of authorization– CKA - Radius change of authorization ACK– CNA - Radius change of authorization NACK

• COMMANDTYPEIndicates the message type. Possible values are:– A - Answer– R - Request

g COMMANDCODE and COMMANDTYPE combined together provide the complete information of the message type.Example: CCR - Credit Control Request

Example: GGSN/GX/CCR - indicates a credit control request message on Gx interface for the peer GGSN.

3.4 Performance countersThis section gives a brief description of all the performance counters used in the current release.

For more information about @Com counters and name of each counters, refer to Counter and Alarms sheet in the Documentation package.

3.4.1 Common countersCounters which are common across CPCS scenarios are described in this section.

3.4.1.1 Push Contexts operation requests Success on local farm

Counter name CtxNoOfPushNormalContexts

Description Number of push context operation requests. Counted when pushing local replication request by the forwarder process successfully

Table 35 Push Contexts operation requests Success on local farm

81


3.4.1.2 Push Contexts operation requests on local farm Error

3.4.1.3 Estimated contexts to be pushed towards remote farm

3.4.1.4 Push Contexts operation requests towards remote farm Success

3.4.1.5 Push Contexts operation requests towards remote farm Error

3.4.1.6 OnRemoteFarm-Estimated context to Push towards remote farm

Counter name CtxNoOfPushNormalContextsErr

Description Number of erroneously push local context replication requests. Counted when pushing local replication request within the forwarder process failed

Table 36 Push Contexts operation requests on local farm Error

Counter name CtxNoOfPushRemoteContextsEstimated

Description Estimation of number of push context remote replica-tion requests to remote. Counted at the instance of ini-tializing Flush.

Table 37 Estimated contexts to be pushed towards remote farm

Counter name CtxNoOfPushRemoteContexts

Description Number of push context remote replication requests. Counted when Pushing remote replication request by the forwarder process successfully

Table 38 Push Contexts operation requests towards remote farm Success

Counter name CtxNoOfPushRemoteContextsErr

Description Number of push context remote replication requests. Counted when Pushing remote replication request by the forwarder process Erroneously

Table 39 Push Contexts operation requests towards remote farm Error

Counter name CtxNoOfPushRemoteContextsEstimatedOtherFarm

Description Counted at the instance of initializing Flush OnRemote-Farm, estimation number of push context remote repli-cation requests towards remote.

Table 40 OnRemoteFarm-Estimated context to Push towards remote farm

82


3.4.1.7 OnRemoteFarm-Push Remote context towards remote farm Success

3.4.1.8 OnRemoteFarm-Push Remote context towards remote farm Error

3.4.1.9 Group contexts currently existing

3.4.1.10 Group contexts currently existing

Counter name CtxNoOfPushRemoteContextsOtherFarm

Description Number of push context remote replication requests on remote farm. Counted when pushing remote replication request by the forwarder process at remote farm suc-cessfully.

Table 41 OnRemoteFarm-Push Remote context towards remote farm Success

Counter name CtxNoOfPushRemoteContextsErrOtherFarm

Description Number of erroneously push context remote replication requests on remote farm. Counted when pushing remote replication request by the forwarder process at remote farm failed

Table 42 OnRemoteFarm-Push Remote context towards remote farm Error

Counter name GrpCtxCurExis

Description Number of group plans configured in oneNDS currently managed on the PCS. Refer to Group quota manage-ment for PCS standalone section in Feature Descrip-tion.

Table 43 Group contexts currently existing

Counter name GrpCtxCurExis

Description Number of group plans configured in oneNDS currently managed on the PCS. Refer to Group quota manage-ment for PCS standalone section in Feature Descrip-tion.

Table 44 Group contexts currently existing

83


3.4.1.11 Gq /Rx terminals max in last period

3.4.1.12 terminals currently existing

3.4.1.13 terminals ever created

3.4.1.14 terminals max in last period

Counter name ActiveContexts

Description maximum number of terminal descriptions (for termi-nals with Gq) simultaneously being present in the PCS instance in the last calculation interval

This is specific to SPDF scenario.Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 45 Gq/Rx terminals max in last period

Counter name TCurrentlyExisting

Description number of terminal descriptions (for terminals with Gq or Gx sessions) currently being present in the PCS instance

Table 46 terminals currently existing

Counter name TEverCreated

Description number of terminal descriptions (for terminals with Gq or Gx sessions) that the PCS instance created since system start

Table 47 terminals ever created

Counter name TCreatedInLP

Description maximum number of terminal descriptions (for termi-nals with Gq or Gx sessions) simultaneously being present in the PCS instance in the last calculation inter-val.

Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 48 terminals max in last period

84


3.4.1.15 Subscribers currently existing

3.4.1.16 Subscribers ever created

3.4.1.17 Subscribers created in last period

3.4.1.18 messages permitted by Policy Rule Engine for ever

3.4.1.19 messages permitted by Policy Rule Engine in last period

Counter name SubsCurrentlyExis

Description number of Subscribers currently attached

Table 49 Subscribers currently existing

Counter name SubsEverCreated

Description number of Subscribers created since system start

Table 50 Subscribers ever created

Counter name SubsCreatedInLP

Description number of Subscribers created in the last calculation interval


Table 51 Subscribers created in last period

Counter name MsgsEverPermitByPRE

Description number of messages permitted by access policy rule engine in PCS instance since system start

Table 52 messages permitted by Policy Rule Engine for ever

Counter name MsgsPermitByPREInLP

Description number of messages permitted by access policy rule engine in PCS instance in the last calculation interval


Table 53 messages permitted by Policy Rule Engine in last period

85


3.4.1.20 messages denied by Policy Rule Engine for ever

3.4.1.21 messages denied by Policy Rule Engine in last period

3.4.2 Gq interface counters

3.4.2.1 valid Gq messages ever received

3.4.2.2 valid Gq messages received in last period

Counter name MsgsEverDnydByPRE

Description number of messages denied by access policy rule engine in PCS instance since system start

Table 54 messages denied by Policy Rule Engine for ever

Counter name MsgsDnydByPREInLP

Description number of messages denied by access policy rule engine in PCS instance in the last calculation intervalLast period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 55 messages denied by Policy Rule Engine in last period

Counter name ValGqMsgsEverRcvd

Description number of valid Gq messages received by the PCS instance since system start

Table 56 valid Gq messages ever received

Counter name ValGqMsgsRcvdInLP

Description number of valid Gq messages received by the PCS instance in the last calculation interval


Table 57 valid Gq messages received in last period

86


3.4.2.3 invalid Gq messages ever received

3.4.2.4 invalid Gq messages received in last period

3.4.2.5 Gq messages ever sent

3.4.2.6 Gq messages sent in last period

3.4.2.7 rejecting Non Overload Gq messages ever sent

Counter name InvGqMsgsEverRcvd

Description number of invalid Gq messages received by the PCS instance since system start

Table 58 invalid Gq messages ever received

Counter name InvGqMsgsRcvdInLP

Description number of invalid Gq messages received by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 59 invalid Gq messages received in last period

Counter name GqMsgsES

Description number of Gq messages sent by the PCS instance since system start

Table 60 Gq messages ever sent

Counter name GqMsgsSentInLP

Description number of Gq messages sent by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 61 Gq messages sent in last period

Counter name RejNoOvldGqMsgsES

Table 62 rejecting Non Overload Gq messages ever sent

87


3.4.2.8 rejecting Non Overload Gq messages sent in last period

3.4.2.9 rejecting overload Gq messages ever sent

3.4.2.10 rejecting overload Gq messages sent in last period

Description number of rejecting Gq messages sent by the PCS instance for any reason except PCS overload since system start

Table 62 rejecting Non Overload Gq messages ever sent (Cont.)

Counter name RejNoOvldGqMsgsSILP

Description number of rejecting Gq messages sent by the PCS instance for any reason except PCS overload in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 63 rejecting Non Overload Gq messages sent in last period

Counter name RejOvldGqMsgsES

Description number of rejecting Gq messages sent by the PCS instance for PCS overload protection since system start

Table 64 rejecting overload Gq messages ever sent

Counter name RejOvldGqMsgsSILP

Description number of rejecting Gq messages sent by the PCS instance for PCS overload protection in the last calcu-lation interval


Table 65 rejecting overload Gq messages sent in last period

88


3.4.3 Rx interface counters

3.4.3.1 valid Rx messages ever received

3.4.3.2 valid Rx messages received in last period

3.4.3.3 invalid Rx messages ever received

3.4.3.4 invalid Rx messages received in last period

Counter name ValRxMsgsEverRcvd

Description number of valid Rx messages received by the PCS instance since system start

Table 66 valid Rx messages ever received

Counter name ValRxMsgsRcvdInLP

Description number of valid Rx messages received by the PCS instance in the last calculation interval


Table 67 valid Rx messages received in last period

Counter name InvRxMsgsEverRcvd

Description number of invalid Rx messages received by the PCS instance since system start

Table 68 invalid Rx messages ever received

Counter name InvRxMsgsRcvdInLP

Description number of invalid Rx messages received by the PCS instance in the last calculation interval


Table 69 invalid Rx messages received in last period

89


3.4.3.5 Rx messages ever sent

3.4.3.6 Rx messages sent in last period

3.4.3.7 rejecting Non Overload Rx messages ever sent

3.4.3.8 rejecting Non Overload Rx messages sent in last period

3.4.3.9 rejecting overload Rx messages ever sent

Counter name RxMsgsES

Description number of Rx messages sent by the PCS instance since system start

Table 70 Rx messages ever sent

Counter name RxMsgsSentInLP

Description number of Rx messages sent by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 71 Rx messages sent in last period

Counter name RejNoOvldRxMsgsES

Description number of Rx messages sent by the PCS instance since system start

Table 72 rejecting Non Overload Rx messages ever sent

Counter name RejNoOvldRxMsgsSILP

Description number of rejecting Rx messages sent by the PCS instance for any reason except PCS overload in the last calculation interval


Table 73 rejecting Non Overload Rx messages sent in last period

Counter name RejOvldRxMsgsES

Table 74 rejecting overload Rx messages ever sent

90


3.4.3.10 rejecting overload Rx messages sent in last period

3.4.3.11 rejecting overload Rx messages which are ever dropped

3.4.3.12 rejecting overload Rx messages dropped in last period

3.4.3.13 Rx sessions currently existing

Description number of rejecting Rx messages sent by the PCS instance for PCS overload protection since system start

Table 74 rejecting overload Rx messages ever sent (Cont.)

Counter name RejOvldRxMsgsSILP

Description number of rejecting Rx messages sent by the PCS instance for PCS overload protection in the last calcu-lation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 75 rejecting overload Rx messages sent in last period

Counter name RejOvldRxMsgsDILP

Description number of rejecting Rx messages sent by the PCS instance for PCS overload protection in the last calcu-lation interval

Table 76 rejecting overload Rx messages which are ever dropped

Counter name RejOvldRxMsgsED

Description indicates number of Rx messages dropped by PCS when message rate or CPU load level is VERY_CRITICAL.


Table 77 rejecting overload Rx messages dropped in last period

Counter name RxSessCurrExis

Table 78 Rx sessions currently existing

91


3.4.3.14 Rx sessions ever created

3.4.3.15 Rx sessions created in last period

3.4.3.16 Rx sessions ever released

3.4.3.17 Number of hanging Rx contexts deleted by PCS

Description number of Rx sessions currently being present in the PCS instance

Table 78 Rx sessions currently existing (Cont.)

Counter name RxSessEverCreated

Description number of Rx sessions that the PCS instance created since system start

Table 79 Rx sessions ever created

Counter name RxSessCreatedInLP

Description number of Rx sessions that the PCS instance created in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 80 Rx sessions created in last period

Counter name RxSessEverReleased

Description number of Rx sessions deleted by PCS as part of session release process which is triggered after a con-nection outage with AF

Table 81 Rx sessions ever released

Counter name RxDeltdHangCtxts

Description number of hanging Rx contexts deleted by PCS

Table 82 Number of hanging Rx contexts deleted by PCS

92


3.4.3.18 Rx Emergency sessions created in last period

3.4.3.19 Rx Emergency sessions currently existing

3.4.3.20 Rx emergency sessions dropped in last period

3.4.3.21 Rx emergency sessions ever created

3.4.3.22 Rx Emergency sessions ever dropped

Counter name RxEmSessCreatInLP

Description number of Rx emergency sessions that the PCS instance created in the last calculation interval (interval duration is configured in PCS/Core/timeIntervalToDumpCounters_s, default is 900 sec)

Table 83 Rx Emergency sessions created in last period

Counter name RxEmSessCurrExis

Description number of Rx emergency sessions currently present in the PCS instance

Table 84 Rx Emergency sessions currently existing

Counter name RxEmSessDILP

Description number of Rx emergency sessions dropped by the PCS instance in the last calculation interval (interval duration is configured in PCS/Core/timeIntervalToDumpCounters_s, default is 900 sec)"

Table 85 Rx emergency sessions dropped in last period

Counter name RxEmSessEverCreated

Description number of Rx emergency sessions that the PCS instance created since system start

Table 86 Rx emergency sessions ever created

Counter name RxEmSessEverDrpd

Description number of Rx emergency sessions that the PCS instance dropped since system start"

Table 87 Rx Emergency sessions ever dropped

93


3.4.3.23 RX Priority Sessions Currently Existing

3.4.3.24 RX Priority Sessions Dropped in Last Period

3.4.3.25 RX Priority Sessions ever dropped

3.4.3.26 RX Priority Sessions Created in Last Period

3.4.3.27 RX Priority Sessions Ever Created

Counter name RxPriSesCurrExis

Description Number of RX Priority Sessions currently existing

Table 88 RX Priority Sessions Currently Existing

Counter name RxPriSesDrpInLP

Description Number of RX Priority Sessions dropped in Last config-ured period

Table 89 RX Priority Sessions Dropped in Last Period

Counter name RxPriSesEvrDrp

Description Number of RX Priority sessions dropped since the system start

Table 90 RX Priority Sessions ever dropped

Counter name RxPriSesCrtInLP

Description Number of RX Priority Sessions created in last config-ured period

Table 91 RX Priority Sessions Created in Last Period

Counter name RxPriSesEvrCrtd

Description Number of RX Priority sessions created since the system start

Table 92 RX Priority Sessions Ever Created

94


3.4.4 Gx interface counters

3.4.4.1 valid Gx messages ever received

3.4.4.2 valid Gx messages received in last period

3.4.4.3 invalid Gx messages ever received

Counter name ValGxMsgsEverRcvd

Description number of valid Gx messages received by the PCS instance since system start

This counter is incremented when a: • Valid Gx request message is received and a

success response is sent. • Valid Gx response message is received

The counter is also incremented when a: • Valid Gx request message is received and a failure

response is sent back for the below reasons • Unable to get session/terminal context. • Unable to get subscriber context • Unable to lock subscriber context and the

message is not queued back

• Valid Gx response message is received with the below failure result • When the peer responds with

UNKNOWN_SESSION

Table 93 valid Gx messages ever received

Counter name ValGxMsgsRcvdInLP

Description number of valid Gx messages received by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 94 valid Gx messages received in last period

Counter name InvGxMsgsEverRcvd

Table 95 invalid Gx messages ever received

95


3.4.4.4 invalid Gx messages received in last period

3.4.4.5 Number of hanging Gx contexts deleted by PCS

3.4.4.6 Gx messages ever sent

Description number of invalid Gx messages received by the PCS instance since system startThis counter is incremented in the following cases based on the incoming message, • Mandatory parameter check fails

This excludes missing of Session-Id, Auth-Applica-tion-Id, Origin-Host, Origin-Realm, Destination-Realm, CC-Request-Type or CC-Request-Number

• Event trigger handling fails • Charging rule report verification fails

Table 95 invalid Gx messages ever received (Cont.)

Counter name InvGxMsgsRcvdInLP

Description number of invalid Gx messages received by the PCS instance in the last calculation interval


Table 96 invalid Gx messages received in last period

Counter name GxDeltdHangCtxts

Description No of Gx Hanging sessions deleted after reauthoriza-tion failed with GGSN Timer to delete the Hangingses-sions can be configured from Gx-Interface in Generalconfig.xml

Table 97 Gx messages ever sent

Counter name GxMsgsES

Description number of Gx messages sent by the PCS instance since system start

Table 98 Gx messages ever sent

96


3.4.4.7 Gx messages sent in last period

3.4.4.8 rejecting Non overload Gx messages ever sent

3.4.4.9 rejecting Non overload Gx messages sent in last period

3.4.4.10 rejecting overload Gx messages ever sent

Counter name GxMsgsSentInLP

Description number of Gx messages sent by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 99 Gx messages sent in last period

Counter name RejNoOvldGxMsgsES

Description number of rejecting Gx messages sent by the PCS instance for any reason except PCS overload since system start

Table 100 rejecting Non overload Gx messages ever sent

Counter name RejNoOvldGxMsgsSILP

Description number of valid Gx messages sent by the PCS instance for any reason except PCS overload in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 101 rejecting Non overload Gx messages sent in last period

Counter name RejOvldGxMsgsES

Description number of rejecting Gx messages sent by the PCS instance for PCS overload protection since system start

Table 102 rejecting overload Gx messages ever sent

97


3.4.4.11 rejecting overload Gx messages sent in last period

3.4.4.12 PDP activations for ever

3.4.4.13 PDP activations in last period

3.4.4.14 Number of successful CCA-I sent for ever

3.4.4.15 Number of successful CCA-I sent in last period

Counter name RejOvldGxMsgsSILP

Description number of rejecting Gx messages sent by the PCS instance for PCS overload protection in the last calcu-lation interval


Table 103 rejecting overload Gx messages sent in last period

Counter name GxPdpActivatesEC

Description Counts the list of Gx-initial messages received since system start

Table 104 PDP activations for ever

Counter name GxPdpActivatesCLP

Description Counts the number of Gx-initial messages received since the last calculation intervalLast period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 105 PDP activations in last period

Counter name GxCCAInitialSuccES

Description Counts the number of successful Gx-initial CCA messages sent since system start.

Table 106 Number of successful CCA-I sent for ever

Counter name GxCCAInitialSuccSILP

Table 107 Number of successful CCA-I sent in last period

98


3.4.4.16 Number of CCR-U received for ever

3.4.4.17 Number of CCR-U received in last period

3.4.4.18 Number of successful CCA-U sent for ever

3.4.4.19 Number of successful CCA-U sent in last period

Description Counts the number of successful Gx-initial CCA messages sent since the last calculation interval.Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 107 Number of successful CCA-I sent in last period (Cont.)

Counter name GxCCRUpdateER

Description Counts the list of Gx-Update messages since system start.

Table 108 Number of CCR-U received for ever

Counter name GxCCRUpdateRILP

Description Counts the list of Gx-Update messages since the last calculation interval.


Table 109 Number of CCR-U received in last period

Counter name GxCCAUpdateSuccES

Description Counts the list of Gx-CCA messages for update since system start.

Table 110 Number of successful CCA-U sent for ever

Counter name GxCCAUpdateSuccSILP

Description Counts the list of Gx-CCA messages for update since the last calculation interval.


Table 111 Number of successful CCA-U sent in last period

99


3.4.4.20 Number of successful RAA received for ever

3.4.4.21 Number of successful RAA received in last period

3.4.4.22 Number of unsuccessful RAA received for ever

3.4.4.23 Number of unsuccessful RAA received in last period

3.4.4.24 Number of RAA timed out for ever

Counter name GxRAASuccER

Description Counts the list of Gx-RAA messages since system start.

Table 112 Number of successful RAA received for ever

Counter name GxRAASuccRILP

Description Counts the list of Gx-RAA messages since the last cal-culation interval.Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 113 Number of successful RAA received in last period

Counter name GxRAAFailER

Description Counts the list of Gx-RAA failure messages since system start.

Table 114 Number of unsuccessful RAA received for ever

Counter name GxRAAFailRILP

Description Counts the list of Gx-RAA failure messages since the last calculation interval.Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 115 Number of unsuccessful RAA received in last period

Counter name GxRAATimeOutER

Table 116 Number of RAA timed out for ever

100


3.4.4.25 Number of RAA timed out in last period

3.4.4.26 Number of CCR-T received for ever

3.4.4.27 Number of CCR-T received in last period

3.4.4.28 Number of successful CCA-T sent for ever

Description Counts the number of Gx-RAA messages time out since system start.

Table 116 Number of RAA timed out for ever (Cont.)

Counter name GxRAATimeOutRILP

Description Counts the number of Gx-RAA messages time out since the last calculation interval.Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 117 Number of RAA timed out in last period

Counter name GxCCRTermER

Description Counts the list of GX-Terminate message's since system start.

Table 118 Number of CCR-T received for ever

Counter name GxCCRTermRILP

Description Counts the list of GX-Terminate message's since the last calculation interval.


Table 119 Number of CCR-T received in last period

Counter name GxCCATermSuccES

Description Counts the list of Gx-CCA messages for terminate since system start.

Table 120 Number of successful CCA-T sent for ever

101


3.4.4.29 Number of successful CCA-T sent in last period

3.4.4.30 Number of GXRAR messages sent for ever

3.4.4.31 Number of GXRAR messages sent in last period

3.4.4.32 Gx Initial Message Rejected in last period

Counter name GxCCATermSuccSILP

Description Counts the list of Gx-CCA messages for terminate since the last calculation interval.Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 121 Number of successful CCA-T sent in last period

Counter name GxRARMsgES

Description Counts the list of Gx-RAR messages sent since system start.

Table 122 Number of GXRAR messages sent for ever

Counter name GxRARMsgSILP

Description Counts the list of Gx-RAR messages sent since the last calculation interval.


Table 123 Number of GXRAR messages sent in last period

Counter name GxReqRejCLP

Description Counts the number of Gx initial messages rejected from PCS in the last calculation interval


Table 124 Gx Initial Message Rejected in last period

102


3.4.4.33 Gx Initial Message Rejected Ever

3.4.4.34 usage limit exceeded in last period

3.4.4.35 usage limit exceeded for ever

3.4.4.36 number of Gx messages dropped when load level is VERY_CRITICAL

3.4.4.37 Gx sessions currently existing

Counter name GxReqRejEC

Description Counts the number of Gx initial messages rejected from PCS since system starts

Table 125 Gx Initial Message Rejected Ever

Counter name GxUsageLimitExcCLP

Description counts the number subscribers for which usage limit exceeded since system startLast period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 126 usage limit exceeded in last period

Counter name GxUsageLimitExcEC

Description Counts the number of Gx initial messages rejected from PCS since system starts

Table 127 usage limit exceeded for ever

Counter name OvldGxMsgsEverDropped

Description number of Gx messages dropped by PCS when message rate or CPU load level is VERY_CRITICAL

Table 128 number of Gx messages dropped when load level is VERY_CRITICAL

Counter name GxSessCurrExis

Description number of Gx sessions currently being present in the PCS instance

Table 129 Gx sessions currently existing

103


3.4.4.38 Gx sessions ever created

3.4.4.39 Gx sessions created in last period

3.4.4.40 Gx bearers currently existing

g This counter is getting updated only in case of multiple bearers in PCS.

3.4.4.41 Gx bearers ever created


3.4.4.42 Gx bearers created in last period


Counter name GxSessEverCreated

Description number of Gx sessions that the PCS instance created since system start

Table 130 Gx sessions ever created

Counter name GxSessCreatInLP

Description number of Gx sessions that the PCS instance created in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 131 Gx sessions created in last period

Counter name GxBearersCurrExis

Description number of Gx bearers currently being present in the PCS instance

Table 132 Gx bearers currently existing

Counter name GxBearersEverCread

Description number of Gx bearers that the PCS instance created since system start

Table 133 Gx bearers ever created

104


3.4.4.43 Gx sessions ever released

3.4.4.44 Gx Emergency sessions created in last period

3.4.4.45 Gx Emergency sessions currently existing

3.4.4.46 Gx emergency sessions dropped in last period

Counter name GxBearersCreadInLP

Description number of Gx Bearers that the PCS instance created in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 134 Gx bearers created in last period

Counter name GxSessEverReleased

Description number of Gx sessions deleted by PCS as part of session release process which is triggered after a con-nection outage with PCEF

Table 135 Gx sessions ever released

Counter name GxEmSessCreatInLP

Description number ofGx emergency sessions that the PCS instance created in the last calculation interval (interval duration is configured in PCS/Core/timeIntervalToDumpCounters_s, default is 900 sec)

Table 136 Gx Emergency sessions created in last period

Counter name GxEmSessCurrExis

Description number of Gx emergency sessions currently present in the PCS instance

Table 137 Gx Emergency sessions currently existing

Counter name GxEmSessDILP

Table 138 Gx emergency sessions dropped in last period

105


3.4.4.47 Gx emergency sessions ever created

3.4.4.48 Gx Emergency sessions ever dropped

3.4.4.49 Gx Priority Sessions Currently Existing

3.4.4.50 Gx Priority Session SPR based created in Last period

3.4.4.51 Gx Priority Session SPR based ever created

Description number of Gx emergency sessions dropped by the PCS instance in the last calculation interval (interval duration is configured in PCS/Core/timeIntervalToDumpCounters_s, default is 900 sec)"

Table 138 Gx emergency sessions dropped in last period (Cont.)

Counter name GxEmSessEverCreated

Description number of Gx emergency sessions that the PCS instance created since system start

Table 139 Gx emergency sessions ever created

Counter name GxEmSessEverDrpd

Description number of Gx emergency sessions that the PCS instance dropped since system start"

Table 140 Gx Emergency sessions ever dropped

Counter name GxPriSessCurrExis

Description Number GX priority sessions currently existing. Include both subscription based and Rx Session based

Table 141 Gx Priority Sessions Currently Existing

Counter name GxPriSprBsdCrtInLP

Description Number of GX Priority session created in last config-ured period based on the subscription

Table 142 Gx Priority Session SPR based created in Last period

Counter name GxPriSprBsdEvrCrtd

Table 143 Gx Priority Session SPR based ever created

106


3.4.4.52 Gx Priority Session SPR based dropped in Last Period

3.4.4.53 Gx Priority Sesions SPR based Ever Dropped

3.4.4.54 Gx Priority Sessions Rx Session Based Created in last Period

3.4.4.55 Gx Priority Sessions RX Session Based ever created

3.4.4.56 Gx Priority Sessions RX session Based Dropped in Last Period

Description Number of GX Priority session created since the system start based on the subscription

Table 143 Gx Priority Session SPR based ever created (Cont.)

Counter name GxPriSprBsdDrpInLP

Description Number of GX Priority session dropped in last config-ured period, which was created based on subscription

Table 144 Gx Priority Session SPR based dropped in Last Period

Counter name GxPriSprBsdEvrDrp

Description Number of GX Priority session dropped since sytem start, which was created based on subscription

Table 145 Gx Priority Sesions SPR based Ever Dropped

Counter name GxPriRxSesBsdCrtInLP

Description Number of GX Priority session created in last config-ured period based on RX session mapping

Table 146 Gx Priority Sessions Rx Session Based Created in last Period

Counter name GxPriRxSesBsdEvrCrtd

Description Number of GX Priority session created since the system start based on the RX sessions mapping

Table 147 Gx Priority Sessions RX Session Based ever created

Counter name GxPriRxSesBsdDrpInLP

Table 148 Gx Priority Sessions RX session Based Dropped in Last Period

107


3.4.4.57 Gx Priority Sessions RX session Based Ever Dropped

3.4.5 Ia interface counters

3.4.5.1 valid Ia messages ever received

3.4.5.2 valid Ia messages received in last period

3.4.5.3 invalid Ia messages ever received

Description Number of GX Priority session dropped in last config-ured period, which was created based on RX Session mapping

Table 148 Gx Priority Sessions RX session Based Dropped in Last Period (Cont.)

Counter name GxPriRxSesBsdEvrDrp

Description Number of GX Priority session dropped since sytem start, which was created based on RX session mapping

Table 149 Gx Priority Sessions RX session Based Ever Dropped

Counter name ValIaMsgsEverRcvd

Description number of valid Ia messages received by the PCS instance since system start

Table 150 valid Ia messages ever received

Counter name ValIaMsgsRcvdInLP

Description number of valid Ia messages received by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 151 valid Ia messages received in last period

Counter name InvIaMsgsEverRcvd

Description number of invalid Ia messages received by the PCS instance since system start

Table 152 invalid Ia messages ever received

108


3.4.5.4 invalid Ia messages received in last period

3.4.5.5 Ia messages ever sent

3.4.5.6 Ia messages sent in last period

3.4.5.7 Ia messages ever dropped

3.4.5.8 Ia messages dropped in last period

Counter name InvIaMsgsRcvdInLP

Description number of invalid Ia messages received by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 153 invalid Ia messages received in last period

Counter name IaMsgsES

Description number of Ia messages sent by the PCS instance since system start

Table 154 Ia messages ever sent

Counter name IaMsgsSentInLP

Description number of Ia messages sent by the PCS instance in the last calculation interval


Table 155 Ia messages sent in last period

Counter name IaMsgsEverDropped

Description number of Ia messages dropped by the PCS instance since system start

Table 156 Ia messages ever dropped

Counter name IaMsgsDroppedInLP

Table 157 Ia messages dropped in last period

109


3.4.6 Sh interface counters

3.4.6.1 valid Sh messages ever received

3.4.6.2 valid Sh messages received in last period

3.4.6.3 invalid Sh messages ever received

3.4.6.4 invalid Sh messages received in last period

Description number of Ia messages dropped by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 157 Ia messages dropped in last period (Cont.)

Counter name ValShMsgsEverRcvd

Description number of valid SH messages received by the PCS instance since system start

Table 158 valid Sh messages ever received

Counter name ValShMsgsRcvdInLP

Description number of valid Sh messages received by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 159 valid Sh messages received in last period

Counter name InvShMsgsEverRcvd

Description number of invalid SH messages received by the PCS instance since system start

Table 160 invalid Sh messages ever received

Counter name InvShMsgsRcdInLP

Table 161 invalid Sh messages received in last period

110


3.4.6.5 Sh messages ever sent

3.4.6.6 Sh messages sent in last period

3.4.6.7 Sh messages Max sent per period

3.4.7 LDAP interface counters

3.4.7.1 invalid Ldap messages ever received

Description number of invalid Sh messages received by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 161 invalid Sh messages received in last period (Cont.)

Counter name ShMsgsEverSent

Description number of Sh messages sent by the PCS instance since system start

Table 162 Sh messages ever sent

Counter name ShMsgsSentinLP

Description number of Sh messages sent by the PCS instance in the last calculation interval


Table 163 Sh messages sent in last period

Counter name ShMsgsSentPP

Description maximum number of Sh messages sent by the PCS instance in a calculation interval since system start

Table 164 Sh messages Max sent per period

Counter name InvLdapMsgsEverRcvd

Description number of invalid LDAP messages received by the PCS instance since system start

Table 165 invalid Ldap messages ever received

111


3.4.7.2 invalid Ldap messages received in last period

3.4.7.3 valid Ldap messages ever received

3.4.7.4 valid Ldap messages received in last period

3.4.7.5 Ldap messages ever sent

3.4.7.6 Ldap messages sent in last period

Counter name InvLdapMsgsRcdInLP

Description number of invalid Ldap messages received by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 166 invalid Ldap messages received in last period

Counter name ValLdapMsgsEverRcvd

Description number of valid Ldap messages received by the PCS instance since system start

Table 167 valid Ldap messages ever received

Counter name ValLdapMsgsRcvdInLP

Description number of valid Ldap messages received by the PCS instance in the last calculation interval


Table 168 valid Ldap messages received in last period

Counter name LdapMsgsEverSent

Description number of Ldap messages sent by the PCS instance since system start

Table 169 Ldap messages ever sent

Counter name LdapMsgsSentinLP

Table 170 Ldap messages sent in last period

112


3.4.8 SoapTrig interface counters

3.4.8.1 invalid subscriber trigger messages ever received

3.4.8.2 invalid subscriber trigger received in last period

3.4.8.3 valid subscriber trigger ever received

3.4.8.4 valid subscriber trigger received in last period

Description number of Ldap messages sent by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 170 Ldap messages sent in last period (Cont.)

Counter name InvSubTrigEverRcvd

Description invalid subscriber trigger messages ever received

Table 171 invalid subscriber trigger messages ever received

Counter name InvSubTrigRcvdInLP

Description number of invalid subscriber trigger received by the PCS instance in the last calculation interval


Table 172 invalid subscriber trigger received in last period

Counter name ValSubTrigEverRcvd

Description number of valid subscriber trigger received by the PCS instance since system start

Table 173 valid subscriber trigger ever received

Counter name ValSubTrigRcvdInLP

Table 174 valid subscriber trigger received in last period

113


3.4.8.5 Rejected Overload SOAP Messages Ever Sent

3.4.8.6 Rejected Overload SOAP Messages Sent in Last Period

3.4.9 SMPP Notification interface counters

3.4.9.1 SMPP Messages Ever sent

3.4.9.2 SMPP Messages Sent In Last Period

Description number of valid subscriber trigger received by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 174 valid subscriber trigger received in last period (Cont.)

Counter name RejOvldSoapMsgsES

Description Counts the number of reject overload soap trigger ever sent by the PCS instance since system start

Table 175 Rejected Overload SOAP Messages Ever Sent

Counter name RejOvldSoapMsgsSILP

Description Counts the number of reject overload soap trigger sent in last period by the PCS instance in the last calculation interval Last period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 176 Rejected Overload SOAP Messages Sent in Last Period

Counter name SMPPMsgsEverSent

Description number of SMPP messages sent by the PCS instance since system start

Table 177 SMPP Messages Ever sent

Counter name SMPPMsgsSentinLP

Table 178 SMPP Messages Sent In Last Period

114


3.4.9.3 SMPP Messages Ever Received

3.4.9.4 SMPP Messages Received In Last Period

3.4.10 GenericPlugin interface counters

3.4.10.1 Plugin Messages Ever Sent

3.4.10.2 Plugin Messages Ever Received

Description number of SMPP messages sent by the PCS instance in the last calculation intervalLast period can be configured from Time-Interval-To-Dump-Counters_s in Serviceconfig.xml file, default is 900 sec.

Table 178 SMPP Messages Sent In Last Period (Cont.)

Counter name SMPPMsgsEverRecvd

Description number of SMPP messages received by the PCS instance since system start

Table 179 SMPP Messages Ever Received

Counter name SMPPMsgsRecvdinLP

Description number of SMPP messages received by the PCS instance in the last calculation interval


Table 180 SMPP Messages Received In Last Period

Counter name pluginMsgsEverSent

Description Counts the number of messages sent to plugin by PCS instance since system start

Table 181 Plugin Messages Ever Sent

Counter name pluginMsgsEverRcvd

Description Counts the number of messages received from plugin by PCS instance since system start

Table 182 Plugin Messages Ever Received

115


3.5 CAF Counters

3.5.1 Common

3.5.1.1 Context operations on local farm

3.5.1.2 Context Replication toward remote farm

Name CtxNoOfSendNormalContexts

Label Send local context replication requests Success

Description Number of send local context replication requests. Counted when sending local replication request by the context manager Successfully

Table 183 Send local context replication requests Success

Name CtxNoOfSendNormalContextsErr

Label Send local context replication requests Errors

Description Number of erroneously send local context replication requests. Counted when sending local replication request within the context manager failed

Table 184 Send local context replication requests Errors

Name CtxNoOfReceivedNormalContexts

Label Received local context replication requests Success

Description Number of received local context replication requests. Counted after receiving local replication request by the context manager successfully

Table 185 Received local context replication requests Success

Name CtxNoOfSendRemoteContexts

Label Send context replication requests toward remote farm Success

Description Number of send context remote replication requests. Counted when sending remote replication request by the context manager success-fully

Table 186 Send context replication requests toward remote farm Success

Name CtxNoOfSendRemoteContextsErr

Table 187 Send context replication requests toward remote farm Error

116


Label Send context replication requests toward remote farm Error

Description Number of erroneously send context remote replication requests. Counted when sending remote replication request by the context manager failed

Name CtxNoOfReceivedRemoteContexts

Label Received context replication request from remote farm Success

Description Number of received context remote replication requests. Counted after receiving the remote replication request by the forwarder process suc-cessfully

Table 188 Received context replication request from remote farm Success

Name CtxNoOfSendForwardContexts

Label Forward Remote context replication requests to Context Manager Success

Description Number of send context forward replication requests. Counted when forwarding replication request from forwarder process to context manager successfully

Table 189 Forward Remote context replication requests to Context Manager Success

Name CtxNoOfSendForwardContextsErr

Label Forward Remote context replication requests to Context Manager Error

Description Number of erroneously send context forward replication requests. Counted when forwarding replication request from forwarder process to context manager failed

Table 190 Forward Remote context replication requests to Context Manager Error

Name CtxNoOfReceivedForwardContexts

Label Received remote replication request from Forward process Success

Description Number of received context forward replication requests. Counted after receiving the forward replication request at the context manager

Table 191 Received remote replication request from Forward process Success

Table 187 Send context replication requests toward remote farm Error

117


3.5.1.3 Context Replication status on remote farm

Name CtxNoOfSendRemoteContextsOtherFarm

Label On remote farm - Send context replication requests toward remote farm Success

Description Number of send context remote replication requests on remote farm. Counted when sending remote replication request by the context manager at remote farm successfully

Table 192 On remote farm - Send context replication requests toward remote farm Success

Name CtxNoOfSendRemoteContextsErrOtherFarm

Label On remote farm - Send context replication requests toward remote farm Error

Description Number of erroneously send context remote replication requests on remote farm. Counted when sending remote replication request by the context manager at remote farm failed

Table 193 On remote farm - Send context replication requests toward remote farm Error

Name CtxNoOfReceivedRemoteContextsOtherFarm

Label On remote farm - Received context replication request from remote farm Success

Description Number of received context remote replication requests on remote farm. Counted after receiving the remote replication request by the for-warder process at remote farm successfully

Table 194 On remote farm - Received context replication request from remote farm Success

Name CtxNoOfSendForwardContextsOtherFarm

Label On remote farm - Forward Remote context replication requests to Context Manager Success

Description Number of send context forward replication requests on remote farm. Counted when forwarding replication request from forwarder process to context manager at remote farm successfully

Table 195 On remote farm - Forward Remote context replication requests to Context Manager Success

118


Name CtxNoOfSendForwardContextsErrOtherFarm

Label On remote farm - Forward Remote context replication requests to Context Manager Error

Description Number of erroneously send context forward replication requests on remote farm. Counted when forwarding replication request from for-warder process to context manager on remote farm failed

Table 196 On remote farm - Forward Remote context replication requests to Context Manager Error

Name CtxNoOfReceivedForwardContextsOtherFarm

Label On remote farm - Received remote replication request from Forward process Success

Description Number of received context forward replication requests on remote farm. Counted after receiving the forward replication request at the context manager on remote farm

Table 197 On remote farm - Received remote replication request from Forward process Success

119


120

Reference Guide Glossary

4 Glossary2G Second generation mobile communications

Current digital cellular system, for example, GSM900/1800/1900, IS-95 (CDMA), IS-136 (TDMA), and PDC.

3G Third generation mobile communications

3G stands for third generation, a generic wireless industry term for high-speed mobile data delivery over cellular networks. 3G networks allow users to send and receive band-width-intensive information such as full-motion video, video conferencing, high quality audio and web data on-demand, virtually anytime and anyplace.

3GPP Third generation partnership projectProject in which standards organizations and other related bodies have agreed to co-operate for the production of globally applicable technical specifications for a third gen-eration mobile system.

3GPP2 Third generation partnership project 2

Project where standards organizations and other related bodies have agreed to co-operate for the production of globally applicable technical specifications for a third gen-eration mobile system.

AAA Authentication, authorization and accountingAAA provides the device with information that is used to authenticate hosts or users (authentication), to assign network privileges (authorisation), and to record user network activity (accounting). In other words it provides an interface between the devices and security servers through which access control can be set up.

AAR Authentication and authorization request

A-BCF Access border control function

Function that provides network address translation (NAT), IP version conversion, and pinholing at the access network border.

A-BGF Access border gateway function

AF Application function

Function that hosts the service logic and communicates the application-level session information to the policy and charging functions. It is a 3GPP network element that supports applications requiring control of Internet Protocol (IP) bearer resources.

AM Application manager

An AM is a system that interfaces to PCS(s) for requesting QoS based services on behalf of end-user. Any given AM communicates with one or more PCS(s) on the oper-ator's network.

AMID Application manager identification

Access Network Collection of network entities and interfaces that provide the underlying IP transport con-nectivity between end user devices and NGN entities.

ANCID Access network charging identifier

119

Reference GuideGlossary

AoC Advice of charge

Is a supplementary service allowing the user paying for a call to be informed of usage-based charging information.

The service may provide the charging information at the end of a call, during a call or at all set-up time.

API Application programming interface

Programming interface that supports the process of developing application programs used to access various network services.

ARACF Access resource and admission control function

It is a functional element performing resource reservation admission control and network policy assembly. A-RACF receives resource reservation requests from SPDF through the Rq interface.

ARPU Average revenue per user or unitARPU is the revenue that a single customer or unit generates. It is usually expressed per month or per year. It is a commonly used measure in the telecommunications indus-try.

AS Application serverServer or a program in a computer in a distributed network that provides the business logic for an application.

A-SBC Access session border control

ASCII American standard code for information interchangeCharacter-encoding standard code developed by the American National Standards Institute (ANSI) to define how computers write and read characters, designed for inter-working between computers.

ATCA Advanced Telecom Computing Architecture

A new series of industry standard specifications for the next generation of carrier grade communications equipment. These specifications are driven by over 100 companies with the PCI Industrial Computers Manufacturers Group (PICMG).

AVP Attribute value pair

Generic pair of values that consists of an attribute header and the corresponding value. It is an information element in a Diameter message.

B&R Backup and restore

BC Border controller

BCF Border control function

Functional entity in a base transceiver station, which handles common control functions and the base transceiver station operation and maintenance functions.

BCID Billing correlation ID

BGF Border gateway function

120


Border gateway function provides the interface between two IP-transport domains. It resides at the boundary between an access network and a core network or between two core networks. The BGF performs both policy enforcement functions and NA(P)T (network address port translation) functions under the control of the SPDF.

B-RAS Broadband remote access server

It is an access server that routes traffic to and from the digital subscriber line access mul-tiplexers on an internet service provider’s network.

CAF Common Application Framework

CAPEX Capital expenditure

Expenditure that consists of the costs of all items purchased or otherwise acquired and entered into the fixed asset register of the entity, or acquisitions of shareholdings in another entity.

C-BGF Core border gateway function

CCA Credit control answer (Diameter)Diameter message that is used between the credit-control server and the Diameter credit-control client to acknowledge a Credit-Control-Request message.

CCR Credit control request (Diameter)Diameter message that is used between the Diameter credit-control client and the credit-control server to request credit authorisation for a given service.

CDMA Code division multiple AccessIt is a technique in which radio transmissions using the same frequency band are coded in a way that a signal from a certain transmitter can be received only by certain receiv-ers. Code division multiple access can be implemented with different kinds of protocols in second-generation (2G) and third-generation (3G) communications.

CE Conformité Européenne

CLF Connectivity session location and repository function

CLI Command line interface

Interface in which the users interact with their computers by typing text into a command line.

CM (1) Cable modemCM is a modulator-demodulator at subscriber locations intended for use in convey-ing data communications on a cable television system.

(2) Configuration managementSet of functions used to control the configuration of the system, that is, to control the extension or reduction of a system, the status of the constituent parts, and the identity of their allocation.Configuration manager (CM) functions allow the system to control the operational parameters, including network element parameters and network element connec-tion parameters.

CMT Chip multi-threading

121


CMT brings to hardware the concept of multi-threading, similar to software multi-thread-ing. CMT-enabled processor, executes many software threads simultaneously within a processor on cores. So in a system with CMT processors, software threads can be executed simultaneously within one processor or across many processors. Executing software threads simultaneously within a single processor increases a processor's effi-ciency as wait latencies are minimized.

CMTS Cable modem termination serverCMTS, located at the cable television system head-end or distribution hub, provides complementary functionality to the cable modems to enable data connectivity to a wide-area network.

Core Network Portion of the delivery system composed of networks, systems equipment and infra-structures, connecting the service providers to the access network.

COPS Common open policy serviceThis is a simple query and response protocol that can be used to exchange policy infor-mation between a policy server and its clients.

CORBA Common object request broker architectureGeneral and open standard for working with distributed objects, developed by the object management group (OMG), allowing the interconnection of objects and applications regardless of the computer language of the applications, the geographical location of the computer, and the architecture of the computers involved OMG.

CSCF Call session control function

Function that establishes, monitors, supports, and releases multimedia sessions, and manages the user's service interactions.

CSP Communication service provider

Is a service provider that provides electronic information transport for its customers. A communications service provider can operate, in wireless, internet, cable, satellite, and managed services businesses.

C-SPDF Core SPDF

DB DatabaseCollection of data describing a specific target area and used and updated by one or more applications.

Diameter Diameter protocol provides a framework for services which require access, authoriza-tion, and accounting as well as policy support across multiple networks. The main function of the Diameter Protocol is to support mobile IP, accounting, network access, and security features. Diameter is also intended to work in both local authentication, authorization, accounting and roaming situations

DOCSIS Data-over-cable service interface specificationA set of interface specifications for transmitting data over cable television systems in a standard fashion.

DoS Denial of serviceDoS is prevention of authorised access to resources or the delaying of time-critical oper-ations. It occurs when an entity fails to perform its proper function or acts in a way that

122


prevents other entities from performing their proper functions. This might be due to a sit-uation where attackers prevent the network users from accessing the network or using the services they are entitled to. Denial of service is also used as a name of an attack.

ETSI European Telecommunication Standards InstituteEuropean standards organization that produces European standards which are applied and accepted in the area of telecommunications

EU European union

FCAPS Fault, configuration, accounting, performance, and security managementConstituent part of the functional architecture of a telecommunications management network (TMN), listed in ITU-T Recommendation M.3010 and described in ITU-T Rec-ommendation M.3400 containing five specific functional areas which are fault, configu-ration, accounting, performance and security management.

FISN Flexi ISN

FM Fault managementConvergence of fixed and mobile services into an integrated service involving the related networks.

FMC Fixed mobile convergenceConvergence of fixed and mobile services into an integrated service involving the related networks.

FTP File transfer protocolApplication protocol, part of the TCP/IP protocol stack, used for transferring files between network nodes.

FTTx Fiber to the xIt is a generic term for any broadband network architecture that uses optical fiber to replace all or part of the usual metal local loop used for last mile telecommunications. The generic term originated as a generalization of several configurations of fiber deploy-ment (FTTN, FTTC, FTTB, FTTH...), all starting by FTT but differentiated by the last letter, which is substituted by an x in the generalization.

FUP Fair usage policy

Gate Gate is the primary logical construct in support of QoS-based service delivery (along with its accompanying authorization token). A PacketCable™ Gate represents a policy-based authorization for a specific envelope of network resources characterized by a suite of QoS parameters. It acts as classifiers for originating and terminating IP addresses and ports, which define and limit the scope of the associated QoS-enhanced flow. A Gate defines a resource authorization envelope consisting of IP-level QoS parameters as well as classifiers defining the scope of Service Flows that may be estab-lished against the Gate.

GBR Guaranteed bit rateGuaranteed number of bits delivered to a service access point (SAP) within a period of time divided by the duration of the period, provided that there is data to deliver

123


The traffic conforms with the guaranteed bit rate as long as it follows a token bucket algorithm where token rate equals the guaranteed bit rate and bucket size equals the maximum service data unit (SDU) size.

GCID (1) GGSN charging identifierIdentifier that consists of the packet data protocol (PDP) context identifier, the asso-ciated flow index into the session description protocol (SDP) from the session initia-tion protocol (SIP) signalling, and the authorisation token associated with the PDP context.

(2) GPRS charging identifier

Charging identifier specific to a PDP context that is generated in the gateway GPRS support node (GGSN) and delivered to the serving GPRS support node (SGSN).

GGSN Gateway GPRS support node

A GGSN is a network node that acts as a gateway between a GPRS wireless data network and other networks such as the Internet or private networks.

GPRS General packet radio service

Mobile service which gives packet-switched access over GSM to external data net-works.

GSM Global system for mobile communication

European digital system for mobile communications.

GTP GPRS tunneling protocolprotocol that is used in the general packet radio service (GPRS) for transmitting user data packets and signaling between GPRS support nodes (GSN) over GPRS backbone network

GUI Graphical user interface

User interface for interacting with computer software based on windows and graphical icons.

HSS Home subscriber server

Master database for a given user, which is used for keeping a list of features and services associated with a user, and for tracking the location of and means of access for its users.

HTTP Hypertext transfer protocol

Protocol utilizing TCP/IP that enables the transfer of HTML files.

ICCM Inventory, configuration and change management

IBCF Interconnection border control functionIBCF provides overall control of the boundary between different service provider net-works. IBCF is located at the border of the home network which connects to the trusted peer networks. IBCF has the most common features with the P-CSCF. IBCF is session stateful, records route itself at initial or standalone requests to be kept in the session sig-naling. IBCF modifies the SIP headers of the forwarded messages if IP version inter-working which is required within the signaling to the particular peer network.

124


Additionally, IBCF checks the trusted status of the particular peer network for which the request is sent to or received from

I-BGF Interconnection border gateway functionIt controls the transport boundary between service provider networks. This function acts as a pinhole firewall and NAT device protecting the service provider’s IMS core. It controls access by packet filtering on IP address/port and opening/closing gates (pin-holes) into the network. It uses network address and port translations (NAPT) to hide the IP addresses/ports of the service elements in the IMS core.

IMS IP multimedia subsystemIt is an open, standardized, operator friendly, next generation networking (NGN) multi-media architecture for mobile and fixed services. It is a VoIP implementation based on a 3GPP variant of session initiation protocol (SIM), and runs over the standard Internet protocol (IP). It is used by telecom operators in NGN networks (which combine voice and data in a single packet switched network), to offer network controlled multimedia ser-vices.

IMSI International mobile subscriber identityUnique subscription identifier that consists of the national mobile subscriber identity (NMSI) and the mobile country code (MCC).

ISN Intelligent service nodeNode that provides service connectivity and application analysis, traffic analysis, and content analysis functions.The intelligent service node enables combined content and traffic charging. It provides the network operator with the possibility to implement a broad variety of charging models suitable for different types of user traffic. The chargeable content can be delivered to the user in such a way that the user is aware of the total costs. The intelligent service node includes GGSN functions, which give the end-user the possibility to use all general packet radio services (GPRS) through a single access point configuration in the mobile terminal. The Intelligent Service Node product is a central element of the Intelligent Content Delivery solution.

IP Internet protocolNetwork layer protocol in the TCP/IP stack that offers a connectionless internetwork service.

IP-CAN IP connectivity access networkThe collection of network entities and interfaces that provide the underlying IP transport connectivity between the UE and the IMS entities. Example: GPRS.The association between a UE and a PDN identifier (for GPRS, APN). The association is identified by a UE IP address together with a UE identity information, if available. An IP-CAN session incorporates one or more IP-CAN bearers. Support for multiple IP-CAN bearers per IP-CAN session is IP-CAN specific. An IP-CAN session exists as long as the UE IP address is established and announced to the IP network.

IP-CAN bearer The data communications bearer provided by the IP-Connectivity Access Network. When using GPRS, the IP-Connectivity Access Network bearers are provided by PDP Contexts.

125


IP Flow A unidirectional sequence of packets identified by OSI Layer 3 and Layer 4 header infor-mation. This information includes source/destination IP addresses, source/destination port numbers, protocol ID. Multiple multimedia streams may be carried in a single IP Flow.

IPv4 Internet protocol version 4

Version 4 of the Internet Protocol.

IPv6 Internet protocol version 6Version 6 of the Internet Protocol with the most important improvement to Internet Protocol version 4 being the generation of more IP addresses. The Internet Protocol version 6 includes support for a flow identifier in the packet header.

I-SPDF Interconnect SPDF

ITU International Telecommunication Union

Telecommunications agency of the United Nations which issues recommendations.

LDAP Lightweight directory access protocolIt is a protocol for accessing directory information, which allows, for example, searching for a distinguished name without revealing the location of the individual

LEMAF Local element management access function

LI Lawful interceptionThe act of intercepting and collecting intercept-related information (IRI) or the commu-nication content (CC) of a transaction and providing that data to a law enforcement mon-itoring facility

Media Component A session can comprise of number of media components such as data, audio, and video.

MEGACO/ MGCP Media Gateway Control ProtocolIETF-ITU-T signalling protocol being used between external call agents and media gateways (MGW) in voice over IP (VoIP) networks. MEGACO is used between the MSC Server and MGW for controlling the MGW. The abbreviation MGCP/Megaco comes from words media gateway control protocol/media gateway control.

MR Media release

MMS Multimedia messaging serviceA messaging service that combines conventional text messages with richer content types, such as photographs, images, sound clips, and video clips. The multimedia mes-saging service is used with multimedia phones, which can receive and process multime-dia messages.

NAC NetAct for Core

NAPT Network address port translationSecond layer of network address translator that maps also transport control protocol (TCP) and user datagram protocol (UDP) ports to new values. Refer NAT.

NASS Network attachment subsystem

126


NASS maintains information about IP-connectivity associated with user equipment con-nected to TISPAN networks. This information is stored in the Connectivity Session Location and Repository Function (CLF) and made accessible to other subsystems and applications through the e4 interface

NAT Network address Translation

Is the process of converting between private and public IPv4 addresses. Generic term for Network Address Translation including NAT-PT and NA(P)T. Denotes the modifica-tion of IP addresses and header fields in IP headers. In NAPT, additionally the port numbers in the transport layer headers are changed. In the context of IMS, NAT may be considered at the edge of the IMS network and at the customer site (for example, xDSL). In case of mixed IPv4/IPv6 environments, NAT-PT is one option to perform a translation between IPv4 and IPv6.

NE Network elementsSystem that can be managed, monitored, or controlled in a telecommunications network, that has one or more standard interfaces, and is identified by a unique man-agement address.

NE3S Nokia Enhanced SNMP Solution Suite

NEM Network element management

Nokia product that provides a complete set of applications for managing network element data, and open interfaces which allow the Nokia network management system NetAct to be smoothly integrated with network elements.

NGN Next generation networkingIt is a broad term to describe some key architectural evolutions in telecommunication core and access networks that will be deployed over the next 5-10 years. The general idea behind NGN is that one network transports all information and services (voice, data, and all sorts of media such as video) by encapsulating these into packets, like it is on the Internet.

NNI Network-network interfaceIt is an interface that allows different networks to interoperate. It can also connect multi-vendor networks. It is standardised by the ITU.

O2ML Operation and maintenance (O&M) modeling language

OAM Operation, administration, and maintenance

Group of network management functions that provide network fault indication, perfor-mance information, and data and diagnosis functions

OCS Online charging system

OCS performs real-time credit control. Its functionality includes transaction handling, rating, online correlation and management of subscriber accounts/balances.

OFCS Offline charging system

OPEX Operator expenditure

Expenditure that consists of all the costs involved in operating a system.

OS Operating system

127


PAP Push application protocol

PCC Policy and charging control

Is a network management tool for packet-switched network access provisioning and network development and optimization.

PCC Rule Policy and charging control rule is a set of information enabling the detection of a service data flow and providing parameters for policy control and/or charging control.

PCEF Policy and charging enforcement function

PCM Policy and configuration manager

PCMM PacketCable MultimediaPCMM defines an architecture to deliver QoS-enabled services over an IP-based cable infrastructure. It enhances the original PacketCable telephony centric architecture to allow flexible support for a broad array of multimedia services.

PCRF Policy and charging rule functionFunction that defines and provides the policy and charging rules that are used in the policy enforcement points for policy control and flow-based charging control. Policy Control Server (PCS) combines policy decision function (PDF) and charging rule function (CRF) to provide resource and charging control for 2G/3G networks.

PCS Policy control serverA system that primarily acts as an intermediary between AM(s) and CMTS(s). It applies network policies to Application Manager requests and proxies messages between the AM and CMTS.

P-CSCF Proxy call state control functionRole of the call state control function which is the first contact point for the packet core network to access the IP telephony network.

PDP Packet data protocolProtocol which transmits data as discrete units known as packets. Packet data protocol is a generic term that refers to standardised packet data protocols such as X.25 or IP.

PDP Context Packet data protocol contexts are required to carry IP packets between a mobile station and the GGSN. A PDP context defines aspects such as routing, QoS, security, billing, and so on. This information is stored in the mobile station and the GPRS support nodes (GSN). The mobile station requires at least one PDP context (the primary PDP context) because the communication between the mobile station and the application server is based on IP and flows over the GGSN. If more PDP contexts are needed, PCS autho-rizes secondary PDP contexts.

PDP Address Packet data protocol address is the IP address of the mobile station.

PDP Policy decision pointSoftware process that functions as a policy server and translator for the policy enforce-ment points under its scope of control.

PEP Policy enforcement point

PNPT Peer network policy table

128


PNT Peer network table

PPP Point-to-point protocol

TCP/IP remote access protocol used to transmit network layer datagrams such as IP packets over serial point-to-point links.

PS Policy server

PSID Policy server identification

QCI QoS class identifier

This number describes the error rate and delay associated with the service.

QoS Quality of serviceIt is a set of quantitative and qualitative characteristics of a distributed multimedia system, which are necessary in order to achieve the required functionality of an applica-tion.

RACS Resource and admission control subsystem

RADIUS Remote authentication dial-in user service

Internet Protocol originally designed for allowing users dial-in access to the Internet through remote servers. Its flexible design has allowed it to be extended well beyond its original intended use.

RCEF Resource control enforcement function

RKS Record keeping serverRKS is a trusted network element component that receives PacketCable™ event messages from other trusted PacketCable™ network elements such as the CMS and CMTS.The RKS also, at a minimum, is a short-term repository for PacketCable™ event messages. The RKS may assemble the Event Messages into coherent sets or call detail records (CDRs), which are then made available to other back office systems such as billing, fraud detection, and other systems.

RTCP Real-time control protocol

RTP Real-time transport protocol

SAS Serial attached SCSISmall computer system interface (SCSI) that implements a serial interface for accessing peripheral devices.

SBC Session border control

S-CSCF Serving call session control functionServing call session control function (S-CSCF) is an IMS element that provides the session control services and is located in the user’s home network. The S-CSCF performs session control and registration services for the user. During the session, the S-CSCF maintains the session state and interacts with the service platforms and charging functions as required by the network operator to provide the services. It performs routing and translation between P-CSCF and IBCF in the I-SPDF scenario.

SCSI Small computer system interface

129


Device-independent interface that is used to connect different peripheral devices, such as disk drives, tape drives, and scanners, to computers.

SDP Session description protocol

SGSN Serving GPRS support nodeGPRS support node that serves GPRS mobile stations by sending or receiving packets through a base station subsystem or a radio access network.

SIP Session initiation protocolA protocol for creating, modifying, and terminating sessions with one or more partici-pants. These sessions include, for example, internet multimedia conferences, internet telephone calls, and multimedia distribution.

SIM Subscriber identity moduleSIM is a security module built on a removable card (SIM card). A SIM card contains its unique serial number, internationally unique number of the mobile user (IMSI), security authentication and ciphering information, temporary information related to the local network, subscription details, and passwords like personal identification number (PIN) and PIN unlock key (PUK).

SMS Short messaging serviceA service that lets the user send and receive text messages of limited length. See also messaging.

SMS-C Short message service centerNetwork element through which short messages are transmitted and in which they can be stored for later transmission if the recipient is not reached.

SMPP Short message peer-to-peer protocolProtocol that is used to transfer e-mail messages. SMTP is usually only used for sending.SMPP is an open, industry standard protocol designed to provide a flexible data com-munications interface for the transfer of short message data between external short message entities (ESME), routing entities (RE) and short message service centers (SMSCs).

SMTP Simple mail transfer protocol

Protocol that is used to transfer e-mail messages. SMTP is usually only used for sending.

SNMP Simple network management protocol

Standard way for computers to share networking information. In SNMP, two types of communications devices exist: agents and managers. An agent provides networking information to a manager application running on another computer. The agent can be polled by the manager, and can also use a message called traps-PDU to send unsolic-ited information to the manager when an unusual event occurs. The agents and managers share a database of information, called the management information base.

SOAP Simple object access protocolIt is lightweight messaging protocol for exchange of information over hypertext transfer protocol (HTTP) in a decentralized, distributed environment. It is based. SOAP provides

130


a way to communicate between applications running on different operating systems, with different technologies and programming languages.

SPDF Service policy decision functionSPDF is a functional element that coordinates the resource reservation requests received from the AF. It is a logical policy decision element for service-based policy control. The SPDF makes policy decisions using policy rules and forwards the session and media related information obtained from the AF to the SPDF for admission control purposes.

SPR Subscriber profile repository

SSH Secure shellProtocol to log into another computer over a network, to execute commands in a remote machine, and to move files from one machine to another.

STA Session termination answer

STR Session termination request

TCP Transport control protocolProtocol that provides the transport service located in the transport layer of the OSI model.

TFT Traffic flow template

TMN Telecommunications Management Network

TISPAN Telecommunications and internet converged services & protocols for advanced networksETSI core competence centre for fixed networks and for migration from switched circuit networks to packet-based networks with an architecture that can serve in both.

TSP Telco service platformTSP is located on top of the different cluster packages and includes middleware func-tions such as the Ticket Manager, the Context Manager, the Communication Manager, and the IP Service Manager.

UDP User datagram protocol

Connectionless transport protocol which provides the exchange of datagrams without acknowledgement or guaranteed delivery.

UE User equipmentOne or more devices allowing an user to access services delivered by TISPAN NGN networks.This includes devices under user control commonly referred to as CPE, IAD, ATA, RGW, and TE but not network controlled entities such as access gateways.

WAP Wireless application protocol

XACML eXtensible access control markup language

XML eXtensible markup language

131

Documents

Pcs Reference Guide