NPS Operating Guide

Nokia Siemens Networks
Profile Server, Rel. 6.1.4,

Operating Documentation, v.1
Operating and maintaining instructions
Operating Guide
DN70274664
Issue 5-0
Approval Date 2010-1-27
Operating Guide
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2010/2/1. All rights reserved
f Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected
has to comply with the applicable safety standards.
The same text in German:

Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-
nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-
zungen und Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die
Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene
Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.
2 Id:0900d805806a281e DN70274664
Issue 5-0
Operating Guide
Table of Contents
This document has 172 pages.
1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.1 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 Operating the Profile Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.1 Browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Accessing the AUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.3 Basic AUI functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.3.1 Entering data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.2 Changing the password and viewing access rights . . . . . . . . . . . . . . . . 15
2.3.3 Accessing the user interfaces of other network elements . . . . . . . . . . . 17
2.3.4 Accessing documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.5 Viewing the About page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4 Logging out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3 Managing operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1 Overview of operator management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.1 Access rights for managing operators . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.2 Creating an operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2.1 Creating an operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2.2 IMSI/MSISDN range validation in provisioning . . . . . . . . . . . . . . . . . . . 23
3.3 Modifying an operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.3.1 Selecting the operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.3.2 Operator details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.3.3 Operator - MMS Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3.4 Operator - templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3.5 Operator - MMS preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.6 Operator - AGW preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.7 Operator - DLS preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.8 Operator - GGSN preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.9 Operator - CA preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.10 Operator - CA preferences - Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.11 Operator - TA preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.3.12 Operator - VoIP preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.4 Deleting an operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4 Managing subscriber types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.1 Overview of subscriber types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.2 Creating a subscriber type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.3 Modifying a subscriber type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.3.1 Selecting the subscriber type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.3.2 Subscriber type - General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.3.3 Subscriber type - MMS preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.3.4 Subscriber type - GGSN preferences . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.3.5 Subscriber type - TA preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
DN70274664 Id:0900d805806a281e 3
Issue 5-0
Operating Guide
4.3.6 Subscriber type - VoIP Server preferences . . . . . . . . . . . . . . . . . . . . . . 44

4.4 Deleting a subscriber type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5 Managing subscribers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.1 Overview of subscriber management . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.2 Creating a subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.3 Modifying a subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.3.1 Wildcards and references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.3.2 Selecting a subscriber. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.3.3 Subscriber - personal information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.3.4 Subscriber - identities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.3.5 Subscriber - subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.3.6 Subscriber - MMS preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.3.7 Subscriber - AGW preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.3.8 Subscriber - DLS preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.3.9 Subscriber - Presence preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.3.10 Subscriber - GGSN preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3.10.1 Subscriber - GGSN preferences - Access points . . . . . . . . . . . . . . . . . . 65
5.3.11 Subscriber - CA preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.3.12 Subscriber - CA preferences - Content subscriptions. . . . . . . . . . . . . . . 67
5.3.13 Subscriber - TA preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
5.3.14 Subscriber - NTMS preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.3.15 Subscriber - VoIP preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.3.16 Subscriber – SMSC preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.3.17 Subscriber – NBG preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.4 Deleting a subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6 Managing services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.1 Overview of service management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.2 Creating an NBG service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.3 Creating an NBG service group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.4 Creating an MMS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.5 Creating an MMS service group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7 Managing corporations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.1 Overview of corporations and short number support . . . . . . . . . . . . . . . 87
7.1.1 Checklist for managing short numbers . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.2 Creating a corporation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.3 Modifying or deleting a corporation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8 Managing MMS application profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9 Distribution lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
9.1 Overview of distribution lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
9.1.1 DL fetch sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9.1.2 Access rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.1.3 Combining DLs with other NPS features . . . . . . . . . . . . . . . . . . . . . . . 101
9.1.4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
9.2 Managing distribution lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
9.2.1 Creating distribution lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4 Id:0900d805806a281e DN70274664
Issue 5-0
Operating Guide
9.2.2 Managing existing lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
10 Managing NTMS groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
11 Managing terminal models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

11.1 Managing terminal models using the AUI . . . . . . . . . . . . . . . . . . . . . . 111
12 Overview of SMSC configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

12.1 Creating new SMSC configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
12.2 Updating existing SMSC configurations. . . . . . . . . . . . . . . . . . . . . . . . 115
13 Managing additional parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

13.1 Managing additional parameters using the AUI . . . . . . . . . . . . . . . . . . 117
13.1.1 Additional parameters - subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
13.1.2 Additional parameters - subscriber type . . . . . . . . . . . . . . . . . . . . . . . 119
13.1.3 Additional parameters - operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
14 Subscriber activity management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

14.1 Creating subscriber activity reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
14.2 Subscriber activity report formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
14.2.1 Activity summary report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
14.2.2 Detailed activity report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
14.2.3 Detailed inactivity report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
15 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
15.1 Viewing current traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
15.2 Creating counter report files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
15.3 Creating transaction log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
15.4 Viewing audit trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
16 System management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

16.1 Managing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
16.2 Managing component groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
16.3 Editing configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
16.4 Viewing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
17 Managing user rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

17.1 Overview of user management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
17.1.1 Examples of user groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
17.2 Managing user groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
17.3 Managing users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
17.4 Changing a network element password. . . . . . . . . . . . . . . . . . . . . . . . 160
18 Managing hunting gourps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

18.1 Overview of hunting groups management . . . . . . . . . . . . . . . . . . . . . . 165
18.2 Creating a hunting group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
18.3 Modifying a hunting group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
18.4 Deleting a hunting group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
DN70274664 Id:0900d805806a281e 5
Issue 5-0
Operating Guide
List of Figures
Figure 1 AUI login page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 2 AUI main page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 3 Current user - change password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 4 Current user - access rights (partial). . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 5 New operator page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 6 Operators page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 7 Operator - details page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 8 Operator - MMS-related settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 9 Operator - template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 10 AGW preferences for operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 11 CA preferences for the operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 12 Operator - CA preferences - New filter . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 13 Operators - CA preferences - Filters - Filter . . . . . . . . . . . . . . . . . . . . . . 36
Figure 14 Entities and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 15 AUI - New subscriber type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 16 AUI - subscriber type selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 17 Subscriber type - General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 18 AUI - subscriber type selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 19 AUI - Subscribers page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 20 AUI - New subscriber page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 21 AUI - Subscribers page with result list . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 22 AUI - Subscriber personal information page . . . . . . . . . . . . . . . . . . . . . . 51
Figure 23 AUI - Subscriber - identities page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 24 AUI - Subscriber's subscription page . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 25 Subscriber - MMS general parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 26 AUI - Subscriber's MMS profile - MMS forwarding rules section . . . . . . 55
Figure 27 AUI - Subscriber's MMS profile - CC rules . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 28 AUI - Subscriber's MMS profile - MO barring . . . . . . . . . . . . . . . . . . . . . 57
Figure 29 AUI - Subscriber's MMS profile - MT barring . . . . . . . . . . . . . . . . . . . . . 59
Figure 30 AUI - Subscriber's MMS profile - Operator's CC rules . . . . . . . . . . . . . . 60
Figure 31 AUI - Subscriber's MMS profile - Operator's MMS MO barring. . . . . . . . 61
Figure 32 AUI - Subscriber's MMS profile - Operator's MT barring. . . . . . . . . . . . . 62
Figure 33 AUI - Subscriber's MMS profile - Services . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 34 AUI - Subscriber AGW preferences page . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 35 AUI - Subscriber DLS preferences page. . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 36 AUI - Subscriber Presence preferences page . . . . . . . . . . . . . . . . . . . . 64
Figure 37 AUI - Subscriber GGSN preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 38 AUI - Subscriber - GGSN preferences - Access points . . . . . . . . . . . . . 65
Figure 39 AUI - Subscriber - GGSN preferences - Access points - service . . . . . . 66
Figure 40 AUI - Subscriber - CA preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 41 Subscriber - CA preferences - New content subscription . . . . . . . . . . . . 68
Figure 42 AUI - Subscriber - TA preferences - New rule set selector . . . . . . . . . . . 69
Figure 43 AUI - Subscriber - NTMS preferences . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 44 AUI - Subscriber - VoIP preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 45 AUI – Subscriber - NBG preferences page. . . . . . . . . . . . . . . . . . . . . . . 73
6 Id:0900d805806a281e DN70274664
Issue 5-0
Operating Guide
Figure 46 AUI - Subscribers page with result list . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Figure 47 AUI – NBG Services page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 48 AUI – Create NBG Services page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 49 AUI – NBG Service details page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 50 AUI – NBG Services page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 51 AUI – Create NBG Service group page . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 52 AUI – NBG Service group details page . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 53 AUI – MMS Services page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 54 AUI – Create MMS Services page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 55 AUI – MMS Service details page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 56 AUI – MMS Services page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 57 AUI – Create MMS Service group page. . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 58 AUI – MMS Service group details page . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 59 New corporation page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 60 Corporation details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 61 Corporation - Short numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 62 AUI - MMS applications page with search results list . . . . . . . . . . . . . . 94
Figure 63 AUI - New MMS application page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 64 DLs and MMS applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Figure 65 Distribution list fetch by the MMS Center. . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 66 AUI - Distribution lists page with search results. . . . . . . . . . . . . . . . . . 103
Figure 67 AUI - New distribution list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 68 AUI - Distribution list members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 69 AUI - MMS application aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 70 AUI - New MMS application alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 71 AUI - NTMS groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 72 AUI - New NTMS group page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 73 AUI - Terminal models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 74 AUI - New terminal model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Figure 75 AUI - Terminal model details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Figure 76 AUI - Additional parameters - subscriber search . . . . . . . . . . . . . . . . . 118
Figure 77 AUI - Additional parameters - subscriber's additional pameters . . . . . 118
Figure 78 AUI - Additional parameters - subscriber type list . . . . . . . . . . . . . . . . 119
Figure 79 AUI - Subscriber activity files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 80 AUI - New subscriber activity summary report. . . . . . . . . . . . . . . . . . . 122
Figure 81 AUI - New subscriber activity report. . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 82 AUI - New subscriber inactivity report . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 83 Current traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 84 AUI - Counter reports default view. . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 85 AUI - Scheduled reports default view. . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 86 AUI- Creating new subscriber report . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 87 AUI- Scheduled subscriber report default view . . . . . . . . . . . . . . . . . . 134
Figure 88 Created report default view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Figure 89 AUI - Transaction log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 90 AUI - New log file page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 91 AUI Audit trail view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 92 AUI - Components page (partial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
DN70274664 Id:0900d805806a281e 7
Issue 5-0
Operating Guide
Figure 93 Component details page for LICAUTH_1 component. . . . . . . . . . . . . . 142

Figure 94 Component details page for MMSCCORE_1 component (partial) . . . . 143
Figure 95 AUI - Component Groups page of NPS running on single machine (partial)
144
Figure 96 Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 97 AUI - Currently open alarms page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 98 AUI - Alarm history page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 99 User group example - Call Center user group . . . . . . . . . . . . . . . . . . . 150
Figure 100 User group example - Network Operator admin . . . . . . . . . . . . . . . . . . 151
Figure 101 User group example - Operator admin . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 102 User group example - MMS application admin . . . . . . . . . . . . . . . . . . . 153
Figure 103 User groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 104 New user group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 105 User group details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 106 User accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 107 New user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 108 User account details - Change password . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 109 Network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 110 Network element details - change password . . . . . . . . . . . . . . . . . . . . 162
Figure 111 AUI – Hunting Groups page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 112 AUI - New group page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 113 AUI – Hunting Group general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Figure 114 Searching result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 115 AUI – Hunting Group general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 116 AUI – Hunting Group members page . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 117 AUI – New Member page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 118 AUI – Update Member page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
8 Id:0900d805806a281e DN70274664
Issue 5-0
Operating Guide
List of Tables
Table 1 Illegal characters in operator ID (VOId) . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 2 Range validation with different configurations . . . . . . . . . . . . . . . . . . . 23
Table 3 Pre-created subscriber templates for the network operator . . . . . . . . . 28
Table 4 Pre-created global subscriber templates . . . . . . . . . . . . . . . . . . . . . . . 30
DN70274664 Id:0900d805806a281e 9
Issue 5-0
Operating Guide
10 Id:0900d805806a281e DN70274664
Issue 5-0
Operating Guide About this document
1 About this document

This document describes how to operate the Nokia Siemens Networks Profile Server
system after the commissioning phase. The operating tasks are mainly performed using
the Administration User Interface (AUI). The document covers the management of
various profile types, traffic reporting, system administration tasks, as well as user right
management features of the AUI.
1.1 Audience
This document is intended for administrators and other personnel who operate the NPS
using the AUI.
1.2 Summary of changes
Date Issue Summary of changes

September 2007 1-0 en First issue for Nokia Profile Server 6.0.
June 2008 2-0 en Updated for Nokia Siemens Networks Profile Server 6.1.
Updated the following sections:
• Operating the Profile server
• Modifying an operator
• Modifying a subscriber type
• Overview of subscriber management
• Creating a subscriber
• Modifying a subscriber
• Changing a network element password
Added the following sections:
• Overview of service management
• Creating an NBG service
• Creating an NBG service group
• Creating an MMS service
• Creating an MMS service group
April 2009 3-0 en Updated for Nokia Siemens Networks Profile Server 6.1
ED2.
Screenshots have been updated.
Updated the following sections:
• Managing subscribers
• Distribution lists
• Managing terminal models
• Managing additional parameters
• Subscriber activity management
Added the following section:
• Managing hunting groups
August 2009 4-0 en Updated screenshots for Nokia Siemens Networks Profile
Server 6.1.3.
DN70274664 Id:0900d805806a2820 11
Issue 5-0
About this document Operating Guide
Date Issue Summary of changes

December 2009 5-0 en Updated screenshots for Nokia Siemens Networks Profile
Server 6.1.4.
1.3 References
Nokia Siemens Networks Profile Server documents
Administration Guide
Integration Guide
Troubleshooting Guide
12 Id:0900d805806a2820 DN70274664
Issue 5-0
Operating Guide Operating the Profile Server
2 Operating the Profile Server

Most of the daily operating and monitoring tasks of the Nokia Siemens Networks Profile
Server (NPS) are performed using the Administration User Interface (AUI). AUI provides
the following capabilities:
• Management of subscribers, subscriber types, subscriptions, MMS applications,
and their service profiles
• Management of operators, their service profiles, and subscriber templates
• Management of distribution lists
• Management of corporations and short number associations
• Management of services and service groups
• Management of NTMS provisioning groups and terminal models
• Management of additional parameters
• Subscriber activity reporting
• Traffic status and reporting
• Viewing and creating audit trail
• Interception of subscribers
• System administration: component management, editing of configuration files,
viewing and cancelling of alarms, and network element access rights
• Management of user account and groups
• SMSC configuration
• Management of hunting groups and members
These capabilities are covered in detail in this document. Users of the NED online doc-
umentation will find the same content in the following NED categories:
• Provision access
• Manage services
• Manage subscriptions
• Administer
• Descriptions
g The search function of the NED package is a powerful tool for locating the desired
documentation module.
2.1 Browser requirements

The AUI is compatible with most modern web browsers. The following browser features
are required:
• Support for frames
• Support for UTF-8 characters
• Support for Javascript
• Popup windows must be allowed
Browser-dependent behaviour may impact your use of the AUI. For example, when you
input data in the AUI fields, it is always best to click the Update button to store the infor-
mation, instead of relying on pressing the Enter key.
The AUI has been tested with the following browsers:
• Internet Explorer 6.0 Service Pack 2
DN70274664 Id:0900d805806a28e7 13
Issue 5-0
Operating the Profile Server Operating Guide
• Netscape 7.01
g Earlier versions of Internet Explorer and Netscape browsers are not compatible.
2.2 Accessing the AUI

The AUI is accessible at the following URL:
http://<hostname of NPS>/
As <hostname of the NPS> you may use any of the following:
• Real IP address of the NPS server
• Real hostname of the NPS server
• Virtual IP address for the prof-ui host
• The virtual prof-ui hostname (must be translated by DNS, or be defined in the hosts
file of the browser machine)
g Using the virtual IP or virtual hostname is recommended if you have a cluster. If
either of the application nodes goes down, the virtual IP address or hostname will
point to the web server on the other node.
To log in, you will have to supply a valid username and password. The capabilities
provided by the AUI depend on the user group to which the user belongs. For informa-
tion on managing user rights, see section Overview of user management.
Figure 1 AUI login page
g After the commissioning of the NPS, the only valid user account for logging in the
AUI is the admin user account. Logging in as the admin user will give you full
access to all capabilities of the AUI. The default password for the admin user is also
admin; you should change this as soon as possible after the commissioning. To
enter the password change page, click on your username at the top of AUI screen.
2.3 Basic AUI functions

After logging in, the main page of the AUI opens. On the left side of the screen is the
navigation menu, which displays links to the resources that the user is allowed to
access. Clicking a link on the navigation menu opens the corresponding page. The
figure below shows all of the resources, since the admin account is logged in:
14 Id:0900d805806a28e7 DN70274664
Issue 5-0
Figure 2 AUI main page

For a detailed explanation of the access rights, see section Overview of access rights in
the Administration Guide. For instructions on how to manage the access rights of users,
see section Overview of user management.
2.3.1 Entering data

When entering data in the various pages of the AUI, you can see which parameters are
mandatory by the asterisk "*" after the name.
After you have completed entering data on a page, you must click the Update button to
commit the changes to the database. Some AUI buttons, such as the Add and Delete
buttons, already show the changes on-screen when they are clicked. However, the
changes are not stored to the database if you do not click the Update button. If you move
from one page to another without clicking Update, the pending changes are lost.
2.3.2 Changing the password and viewing access rights

All users who have logged in to the AUI can change their password and view their
access rights by clicking their username at the top of the page.
g Naturally also the admin user can change users' passwords; see section Managing
users for details.
DN70274664 Id:0900d805806a28e7 15
Issue 5-0
Figure 3 Current user - change password

To change the password, the user must enter the old password, and the new password
twice. The change will be effective immediately after clicking the Change password
button.
Users may also view their access rights by clicking the Access rights tab:
16 Id:0900d805806a28e7 DN70274664
Issue 5-0
Figure 4 Current user - access rights (partial)

Access rights cannot be edited on this page.
2.3.3 Accessing the user interfaces of other network elements

If desired, you can add links to the user interfaces of Nokia Siemens Networks MMS
Center and Nokia Siemens Networks Application Gateway (AGW) in the NPS AUI. This
will enable you to switch to the user interfaces of the MMS Center and the AGW from
the NPS AUI. For configuration instructions, see section Configuring AUI in the Admin-
istration Guide.
2.3.4 Accessing documentation

The Documentation link at the top right corner of the page can be configured to open
the front page of a locally installed documentation package. For instructions on how to
do this, see section Configuring AUI in the Administration Guide.
2.3.5 Viewing the About page

When the About link at the top right corner of the page is clicked, a page will open which
displays general information of the product, including the software version.
The version number that is visible in the AUI does not necessarily reflect the latest
installed minor version. If a delivery does not contain any changes to the AUI function-
ality (for example, NPS 6.0), the version change may not be reflected on the About
page.
DN70274664 Id:0900d805806a28e7 17
Issue 5-0
2.4 Logging out

Clicking Log Out at the top of the page will end the session and log the current user out
of the AUI. The user's session will also expire after 30 minutes of inactivity, after which
the user must log in again.
The caching features of web browsers are a security threat, since the browser can cache
the username and password of the user. For example, it may be possible to use the
Back and Refresh buttons to access the AUI without having to enter the username and
password again. The exact security threat depends on the browser type and configura-
tion, and may not be present in all browsers.
To avoid the immediate threat of someone else using the AUI with their access rights,
all users should remember to close their browser application after logging out of the AUI,
and to clear the browser cache at appropriate intervals.
18 Id:0900d805806a28e7 DN70274664
Issue 5-0
Operating Guide Managing operators
3 Managing operators
3.1 Overview of operator management

Operator entities are usually managed using the AUI, although it is also possible to
perform operations on operators using the Profile Interface.
For instructions on creating an operator, see section Creating an operator.
For instructions on modifying an operator's settings, see section Modifying an operator.
For instructions on how to delete an operator entity, see section Deleting an operator.
g Section Checklist for creating a virtual operator in the Virtual Operator Guide
document is a good resource for verifying that all necessary actions are taken when
a new operator is created.
3.1.1 Access rights for managing operators

Access to the operator management section of the AUI is controlled by the Operators
& Additional parameters resource. User groups with access to this resource can
create, modify and delete operator entities. Operator-specific user accounts are limited
to managing the settings of their own operator, and any sub-operators that may have
been created for their operator.
DN70274664 Id:0900d8058052bfdf 19
Issue 5-0
Operating Guide
3.2 Creating an operator
3.2.1 Creating an operator

Purpose
This procedure provides instructions for creating a new operator entity in the Nokia
Siemens Networks Profile Server (NPS).
Before you start

You can only create new operators if the Virtual Operator support feature is enabled by
the license.
Steps
1 Log in to the AUI as a user with access to the Operators & Additional parameters
resource.
2 Click Operators in the vertical menu.
3 On the Operators page, click New. The New operator page opens.
Figure 5 New operator page
4 Enter the name and Operator ID (VOId) for the new operator.
VOId is the unique string by which the operator is recognized in NPS. All subscribers of
this operator will have the same VOId in the database. In the NPS, the VOId string may
be up to 43 characters long, and may contain spaces.
g The Nokia Siemens Networks MMS Center requires that the VOId is a fully qualified
domain name (FQDN), for example operator.com. For compatibility, it is recom-
mended that you set a fully qualified domain name as the VOId even if you are cur-
rently not using the MMS Center with NPS.
20 Id:0900d8058052bfe3 DN70274664
Issue 5-0
Operating Guide
The following characters are not allowed in the VOId:
" (quotation) % (percentage)

' (apostrophe) : (colon)
& (ampersand) ; (semicolon)
< (less than) , (comma)
> (greater than) \n (newline)
= (equals) \t (horizontal tab)
+ (plus) \b (backspace)
/ (slash) \f (form feed)
\ (backslash) \r (carriage return)
Table 1 Illegal characters in operator ID (VOId)
Examples of valid VOId strings:

operator.com
telco.net
my.operator.fi
g The VOId string unknown is reserved for use by the reporting subsystem. Do not
use it.
5 If you want to make the new operator a subordinate operator (sub-VO) for an
existing operator, select the Owner VO from the drop-down menu.
Sub-VOs are complete operators with their own subscribers, service profiles and admin-
istrators. However, the Owner VO can limit the services available to the sub-VO, and
optionally access the subscriber base of the sub-VO.
6 Click Add to open a field for an operator resolution rule.

The resolution rules are used during profile fetch events to determine the operator to
which a subscriber belongs, for example in autoprovisioning cases. Resolution rules can
also be used to validate that subscriber is provisioned to the correct operator. For more
information on this feature, see section IMSI/MSISDN range validation in provisioning.
Each VO resolution rule consists of a subscriber identity type and a pattern of values.
You can define rules based on three identity types:
• MSISDN/MDN
• IMSI
• Email
For MSISDN/MDN and IMSI, the pattern of values must be a nonempty string that ends
with an asterisk “*” (e.g. “050*”). For Email, the string must begin with the asterisk, and
contain the "@" character. (e.g. "*@operator.com", "*@*")
The resolution rules must be unique among the operators. For example, if one operator
already has the rule MSISDN/MDN=123*, no other operator may have such an identical
rule. However, overlapping rules are allowed. For example, another operator can have
DN70274664 Id:0900d8058052bfe3 21
Issue 5-0
Operating Guide
the rule MSISDN/MDN=12*. If this results in multiple rules matching a subscriber, the
strictest rule will win.
No resolution conflicts are allowed; each subscriber must be resolved to exactly one or
zero operators. If a subscriber is resolved to more than one operator, a VO resolution
error is returned to the network element which performed the profile fetch.
g If the resolution rules are changed after subscribers have already been created or
updated, there can be conflicting VO – subscriber combinations in the database.
The same applies if the IMSI/MSISDN range validation feature is taken into use
afterwards. Checking is done only at that point when subscriber is being created or
updated.
Remember to change the resolution rules for existing operators so that they do not
conflict with the new operator's rules.
g If Mobile Number Portability (MNP) is used, the profile resolution rules should be
based on IMSI. Furthermore, the MMS Center should always send also the IMSI of
the subscriber to Profile Server.
7 When done, click Create.

The Operator - Details page opens. Continue configuring the operator's settings
according to the instructions in section Modifying an operator
Further information
Every operator needs at least one subscriber type. Don't forget to create a subscriber
type for the operator as instructed in section Creating a subscriber type.
For more information on subscriber types, see section Overview of subscriber types.
22 Id:0900d8058052bfe3 DN70274664
Issue 5-0
Operating Guide
3.2.2 IMSI/MSISDN range validation in provisioning

If the IMSI/MSISDN range validation is enabled, the MSISDN/MDN or IMSI numbers are
verified for subscribers that are created or updated so that they match to the existing res-
olution rules of the operator used in provisioning. By default, this feature is not enabled.
To enable range validation for AUI, add and update operations by setting the following
parameter in the ui.properties file:
nap.core.ui.subscriber.resolvedVOCheck.enabled=true
The table shows how this feature works with different configurations.
• “Own VO” means subsciber is given to an operator that has a matching rule.
• “Not own VO” means subscriber belongs to some other operator than the one to
which it is being given.
If there are no matching resolution rules found, the “VO not found” case is applicable.
resolvedVOCheck.enabled rejectWhenVONotFound Own Not VO not

VO own found
VO
true true Ok Not Not ok
ok
true false Ok Not Ok
ok
false N/A Ok Ok Ok
Table 2 Range validation with different configurations
Example:
Range validation with two operators
Create two operators with the following information:
• VOA Resolution rules: MSISDN/MDN=1*
• VOB Resolution rules: MSISDN/MDN=2*
MSISDN/MDN VOId Result

1234 VOA Ok
1234 VOB Error
1234 VOB Ok, when the property
rejectWhenVONotFound is
false
1234 VOB Error, when the property
rejectWhenVONotFound is
true
Range validation can be enabled also for CSV and Profile Interface (PI). For information
on how to configure the property files dataprovisioning.properties and
prov.properties, see Parameter Reference.
DN70274664 Id:0900d805804436f1 23
Issue 5-0
Operating Guide
3.3 Modifying an operator

This section presents the configuration options for operator entities in the Nokia
Siemens Networks Profile Server (NPS). Follow the instructions in this section when
configuring the operator(s) in your system.
When modifying an operator's settings, remember to click Update to commit your
changes before moving to anotber page. Otherwise, the changes you have made will be
lost.
3.3.1 Selecting the operator

1. Log in to the AUI as a user with access to the Operators & Additional parameters
resource. Note that operator-specific users only have access to their own operator's
settings, and to the settings of any operators that are subordinate to their operator
(sub-VOs).
2. Click Operators in the vertical menu. The Operators page opens.
3. You see a list of the operator entities that you can configure. Click the name of an
operator entity to select it.
Figure 6 Operators page

The following sections present the data which is available for the operator by clicking the
tabs on the horizontal navigation bar. If you change any data, remember to click Update
to save the changes.
3.3.2 Operator details

On this page, you can set the basic information for the operator. Only the admin and non
operator-specific users can see and edit all fields on this page.
• Operator ID
This is the unique VOId value of the operator.
• Name
The name with which the operator is know in NPS. Note: VOId is the actual identifier
used in all operations. The name is only for convenient usage in GUI.
• Resolution rules
These are the rules according to which operators are resolved in profile fetches. For
more information, see section Creating an operator.
• Capacity limit
Defines the maximum profile fetch capacity that this operator can use. The limit is
defined in requests/second, and is shared by all profile fetch interfaces for this oper-
24 Id:0900d8058052c002 DN70274664
Issue 5-0
Operating Guide
ator. This field does not have a meaning for Sub-VOs, since they can always use the
full profile fetch capacity of their owner operator.
• Owner VO
Defines the operator that owns the current operator (making the current operator a
sub-VO). Operators that have sub-VOs cannot be owned by other operators.
• MMS enabled - Allows the use of the MMS profile fetch.
• AGW enabled - Allows the use of the AGW profile fetch.
• DLS enabled - Allows the use of the DLS profile fetch.
• Presence enabled - Allows the use of the Presence profile fetch.
• Advertising Enabled - Allows advertising messages to be sent.
When advertising has been enabled, messages with advertising content can be sent
to the subscribers belonging to this operator. However, if the NPS targeted advertis-
ing support feature has been disabled for the subscriber or subscriber type,
messages will not be sent. For more information on this feature, see NPS targeted
advertising support in the Product Description.
• Interests - List of interests that will be used as a default setting for the subscribers
belonging to this operator if interests have not been defined on the subscriber or
subscriber type level.
If a service is not selected for the operator, the corresponding link to the operator's
service profile is hidden from the operator's AUI page. The service profiles of the sub-
scribers and subscriber types can be edited normally in the AUI, and provisioned
normally through the data provisioning interfaces. However, service profiles cannot be
fetched through the profile fetch interfaces if the service is not enabled for the operator.
g Additionally, the profile fetch interfaces must be enabled in the license files of the
NPS.
DN70274664 Id:0900d8058052c002 25
Issue 5-0
Operating Guide
Figure 7 Operator - details page
3.3.3 Operator - MMS Details

On this page, you can set the following MMS-related settings:
• Maximum MMS recipients
Sets the maximum number of recipients one MMS message may have, between 0
and 99. If there are more recipients than the value allows, the message is barred.
Value 0 means no recipients are allowed. When MMS is sent to a distribution list,
each list is counted as one recipient.
• MMS sending to all operators
If set, the subscribers of this operator may send MMS messages to subscribers of
other operators.
26 Id:0900d8058052c002 DN70274664
Issue 5-0
Operating Guide
• Update MMS terminal capability in originator MMS profile fetch

If set, the MMS terminal capability of an MMS message originator is set to the value
defined in Update to selected value drop-down menu.
• Update MMS terminal capability in receiver MMS profile fetch
If set, the MMS terminal capability of an MMS message receiver is set to the value
defined in Update to selected value drop-down menu.
• Update MMS terminal capability in receiver terminal type update
If set, the MMS terminal capability of an MMS message receiver is set to the value
defined in Update to selected value drop-down menu when the MMS Center
performs a terminal type update.
• MMS terminal types
This is an operator-specific list which maps a terminal string to a terminal capability.
Using the Add button, you can add mappings to the list.
The NPS uses these mappings when the MMS Center requests for an MMS origi-
nator profile, or sends an update in response to an MMS receiver profile. The
terminal string in the request is compared to the mapping list, and the MMS capabil-
ity field in the subscriber's MMS profile is updated if necessary.
• Allow read reply report for MMS senders
If set, MMS message originators are allowed to request read-reply reports, which
inform the originator that the receiver has read the message.
• Allow delivery report for MMS senders
If set, MMS message originators are allowed to request delivery reports, which
inform the originator that the receiver has received the message.
DN70274664 Id:0900d8058052c002 27
Issue 5-0
Operating Guide
Figure 8 Operator - MMS-related settings
3.3.4 Operator - templates

Subscriber templates are actual subscriber entities in the NPS database which are used
as default data for profile fetch responses and autoprovisioned subscribers. Subscriber
templates are created, edited and deleted just like real subscribers, and they are identi-
fied by their MSISDN/MDN. The subscribers that are assigned as templates must
belong to the current operator.
g The unique identities of the subscriber template (such as MSISDN/MDN, IMSI, and
email) are not copied when the template is used.
After the NPS installation, several subscriber templates have already been defined and
assigned for the network operator. The MSISDN/MDNs of these templates are as
follows:
MSISDN / MDN Template

1 Default MMS originator
Table 3 Pre-created subscriber templates for the network operator
28 Id:0900d8058052c002 DN70274664
Issue 5-0
Operating Guide
MSISDN / MDN Template

2 Default MMS recipient
3 MMS autoprovisioning template (originator)
5 Default DLS profile
6 DLS autoprovisioning template
8 MMS autoprovisioning template (legacy receiver)
15 MMS autoprovisioning template (multimedia-enabled receiver)
Table 3 Pre-created subscriber templates for the network operator (Cont.)
g Future releases of NPS may create additional subscriber templates. For that
reason, the MSISDN/MDN range 1-100 is reserved for use by the NPS product.
When creating new subscriber templates, do not reserve MSISDN/MDN numbers in
this range, as it may cause problems during NPS upgrades.
The Operator - templates page contains the following settings for the operator:
• Default subscriber type
This subscriber type is used as the default subscriber type when Service Aware
autoprovisioning creates a subscriber for this operator. The drop-down menu
contains the subscriber types that exist for the current operator.
For more information on ICD autoprovisioning, see section Configuring Service
Aware autoprovisioning in the Integration Guide.
• Originator MMS autoprovisioning enabled
This flag enables autoprovisioning for MMS originator profile fetch events. Enter the
MSISDN/MDN of the template to be used in the Template field.
• Receiver MMS autoprovisioning enabled (legacy users)
This flag enables autoprovisioning for MMS receiver profiles. If the receiver of an
MMS is not in the NPS database, it will be created. Enter the MSISDN/MDN of the
template to be used in the Template field.
• Receiver MMS autoprovisioning enabled (multimedia users)
This flag enables autoprovisioning for MMS receiver terminal update events. This
autoprovisioning type creates a subscriber in the NPS database when a terminal
type update is received from the MMS Center (this guarantees that the subscriber is
MMS enabled). Enter the MSISDN/MDN of the template to be used in the Template
field.
• DLS autoprovisioning enabled
This flag enables autoprovisioning for DLS profile fetch events. Enter the
MSISDN/MDN of the template to be used in the Template field.
• Originator default profile enabled
This flag enables the default MMS originator profile. When enabled, the default orig-
inator profile is returned as a response to MMS originator profile fetch when the sub-
scriber is not found in the database.
Enter the MSISDN/MDN of the template to be used in the Template field. The MMS
service profile of this subscriber will be used.
DN70274664 Id:0900d8058052c002 29
Issue 5-0
Operating Guide
• Receiver default profile enabled

This flag enables the default MMS receiver profile. When enabled, the default
receiver profile is returned as a response to MMS receiver profile fetch when the
subscriber is not found in the database.
Enter the MSISDN/MDN of the template to be used in the Template field. The MMS
• Default profile enabled
This flag enables the default DLS profile. When enabled, the default receiver profile
is returned as a response to DLS profile fetch when the subscriber is not found in
the database.
Enter the MSISDN/MDN of the template to be used in the Template field. The DLS
The changes in the templates and enabled features are taken into use right away.
Figure 9 Operator - template

In addition to the subscriber templates mentioned in the beginning of this section, NPS
also uses subscriber templates for autoprovisioning and default profile features which
do not fully support the virtual operator concept. The following global templates are pre-
created during NPS installation under the network operator (with subscriber type
default):
MSISDN / MDN IMSI Template

7 (none) NTMS autoprovisioning template
9 9 GGSN default profile
10 10 GGSN autoprovisioning template
11 11 CA default profile
Table 4 Pre-created global subscriber templates
30 Id:0900d8058052c002 DN70274664
Issue 5-0
Operating Guide
MSISDN / MDN IMSI Template

12 12 CA autoprovisioning template
13 13 TA default profile
14 14 TA autoprovisioning template
Table 4 Pre-created global subscriber templates (Cont.)
These templates are common for all VOs in the system, and are not modifiable on the
Operator - templates page. Please see the following sections in the Integration Guide
for more information and configuring instructions:
• Configuring MMS autoprovisioning
• Configuring NTMS autoprovisioning
• Configuring Service Aware autoprovisioning
3.3.5 Operator - MMS preferences

On this page, the operator sets the MMS service default profile. If a subscriber or sub-
scriber type does not define a value for an MMS profile parameter, the operator's service
default will be used. For more information on profile resolution, see section Profile res-
olution in the Technical Reference document.
The MMS preferences page contains a large amount of MMS profile settings, divided in
eight categories. To move from one category to another, click the name of the category
in the horizontal menu that appears on the MMS preferences page. After entering any
data, be sure to click the Update button at the bottom of the page to commit your
changes. Otherwise, moving between the categories will clear the newly entered data.
The categories for MMS profile settings are:
• General
• Forwarding
• CC rules
• MO barring
• MT barring
• Operator's CC rules
• Operator's MO barring
• Operators's MT barring
The content of the categories is the same as in the MMS service profile of a subscriber.
For more information on the fields and their meaning, refer to section Subscriber - MMS
Preferences.
3.3.6 Operator - AGW preferences

On this page, the operator sets the AGW service default profile. If a subscriber's profile
does not define a value for an AGW profile parameter, the operator's service default will
be used. Except for the COS value, the subscriber's AGW service profile cannot be
directly edited from the AUI. The editing should be done from the AGW GUI.
The fields on this page are:
• Rules editing enabled: If set, rule editing is enabled for the subscriber in the AGW.
DN70274664 Id:0900d8058052c002 31
Issue 5-0
Operating Guide
• Anonymous enabled: This flag is not currently used by the AGW, and can be
ignored.
• VGW PIN: The VGW PIN number of the subscriber.
• Secondary email addresses: Additional email addresses for the subscriber. Click
the Add button to create a new field for entering an address.
• Device email: This field must always contain a reference to the subscriber's
MSISDN, followed by the operator's domain. The reference part should be written
exactly as follows (no spaces):
${subscrmsisdn}
For example:
${subscrmsisdn}@operator.com
• AGW password: The AGW password of the subscriber.
• AGW password expiration date: The expiration date of the subscriber's AGW
password. Not currently used by AGW. The format for the field is yyyy.mm.dd. For
example: 2009.12.31
• Additional parameters: Click the Add button to enter a new parameter-value pair.
Figure 10 AGW preferences for operator
3.3.7 Operator - DLS preferences

On this page, the operator sets the DLS service default profile. If a subscriber's profile
does not define a value for an DLS profile parameter, the operator's service default will
be used. The fields on this page are the same as in the DLS service profile of a sub-
scriber, except for the DLS user name field which is not included.
For more information on the fields and their meaning, refer to section Subscriber - DLS
Preferences.
32 Id:0900d8058052c002 DN70274664
Issue 5-0
Operating Guide
3.3.8 Operator - GGSN preferences

On this page, the operator sets the GGSN service default profile settings and access
points. These settings and access points are used if there is no GGSN service profile
content in the profile of the subscriber and the subscriber type. If any parameters or
access points are defined in the subscriber or subscriber type profile, the operator's
profile is not considered at all.
The fields on this page, and the creation of the access points, are the same as in the
GGSN service profile of a subscriber. For more information, refer to section Subscriber
- GGSN Preferences.
3.3.9 Operator - CA preferences

This page is used to set the operator's CA service preferences. These preferences are
not the same as the subscriber's CA service profile; the operator does not have the
same kind of service profile for the CA service.
• CA operator ID
ID of the profile (unique among the operator profiles). This ID is generated by NPS,
and cannot be changed.
• Description
Internal description of the operator profile.
• Required roaming access service
The contentServiceId of the linked roaming access service. Indicates that
access subscription is required when a subscriber is roaming.
• Content size
The from value defines the size of content (in kB) that triggers price indication. The
to value (in kB) is the maximum size that can be delivered from a content service.
An error message will be shown for bigger content.
• Content price
The from value defines the minimum price of commercial content after which the
price indication is shown e.g. "4.25 EUR" or "4.25 EUR%17.25" where the tax per-
centage is optionally defined after the hash character. The to value defines the
maximum price of commercial content the operator's subscribers can download.
The format is the same as for the from value.
• Allowed content services
This section contains two lists. The Available services list contains the service IDs
that have been fetched from the ISD. You can add services from this list to the
Allowed services list by selecting the service ID and clicking the Add button
between the lists. To remove a service from the list, select the service and click
Remove.
• Allowed content service groups
This section contains two lists. The Available groups list contains the service
groups that have been fetched from the ISD. You can add service groups from this
list to the Allowed groups list by selecting the service group ID and clicking the Add
button between the lists. To remove a service group from the list, select the group
ID and click Remove.
• Additional parameters
This section contains additional parameters and values that have been defined for
the operator's CA profile. Pressing the Add button creates two new fields where you
DN70274664 Id:0900d8058052c002 33
Issue 5-0
Operating Guide
can enter a new parameter and its value. Parameters can be deleted using the cor-
responding Delete button on the right.
Figure 11 CA preferences for the operator
3.3.10 Operator - CA preferences - Filters

The Filters tab on the Operator - CA preferences page opens a page which displays
the list of existing service filters for this operator. The page also contains a tab for
creating a new filter.
Filters are a way to make services unavailable according to time-based rules. For
example, you can create a filter that disallows access to certain services between 8:00
and 16:00 from Monday to Friday.
When creating a new filter, you first have to enter a Description and the Applied hours
when the filter is in effect.
34 Id:0900d8058052c002 DN70274664
Issue 5-0
Operating Guide
The format for the Applied hours value is a comma-separated list of ranges, where a
range is in the format day:hour-day:hour. The day is entered using a three letter
abbreviation (Mon | Tue | Wed | Thu | Fri | Sat | Sun) and the hour is an integer between
0 and 23, or an asterisk "*".
Examples:
• Mon:08-Fri:16 applies from Monday 08:00 to Friday 16:00 (including nights).
• Mon:*-Mon:*,Wed:*-Wed:* applies for the whole Monday and Wednesday.
Figure 12 Operator - CA preferences - New filter

After you create a new filter (or click the name of an existing filter in the list), a page
opens where you can edit the content of the filter. In addition to the Description and
Applied hours, you can set the following:
• Barred addresses
Clicking the Add button opens a field where you can define an IP address where the
operator's subscribers are not allowed to make requests to. All other addresses are
allowed by default. The format is IP address[/netmask]:[URL].
You can define multiple barred addresses by clicking the Add button to open new
fields.
• Barred content services
This section contains two lists. The Available services list contains the service IDs
that have been fetched from the ISD. You can add services from this list to the
Barred services list by selecting the service ID and clicking the Add button between
the lists. To remove a service from the list, select the service and click Remove.
• Barred content service categories
This section contains two lists. The Available categories list contains the service
groups that have been fetched from the ISD. You can add service groups from this
list to the Barred categories list by selecting the service group ID and clicking the
Add button between the lists. To remove a service group from the list, select the
group ID and click Remove.
DN70274664 Id:0900d8058052c002 35
Issue 5-0
Operating Guide
Figure 13 Operators - CA preferences - Filters - Filter
3.3.11 Operator - TA preferences

The TA preferences page is used to create and manage the rule set selectors in the
operator's TA profile. These rule set selectors are used if there are no rule set selectors
defined in the TA service profile of the subscriber and the subscriber type. If any rule set
selectors are defined in the subscriber or subscriber type profile, the rule set selectors
in the operator's TA profile are not considered at all.
The page opens a page which displays the list of existing rule set selectors for this oper-
ator. Clicking the name of a rule set selector opens it for editing, and clicking the New
button opens the page for creating a new rule set selector. The rule set selectors are
created and edited in the same way as in the subscriber's TA service profile. For more
information, see section Subscriber - TA preferences.
36 Id:0900d8058052c002 DN70274664
Issue 5-0
Operating Guide
3.3.12 Operator - VoIP preferences

On this page, the operator sets the VoIP service default profile. Only three parameters
can be defined on the operator level; Group Profile ID, Location ID and
Authentication Profile ID. If the parameters are not defined on the subscriber or sub-
scriber type level, the operator's defaults are used.
For more information on the fields and their meaning, refer to section Subscriber - VoIP
Preferences.
DN70274664 Id:0900d8058052c002 37
Issue 5-0
Operating Guide
3.4 Deleting an operator

Purpose
To delete an operator entity.
Before you start

You will not be able to delete an operator entity if it has any child entities such as sub-
scribers, subscriber types, or users.
Steps
1 Log in AUI as a user with access to the Operators & Additional parameters
resource.
If you log in as an operator-specific user, you will only see your own operator and any
subordinate operators (sub-VOs) that have been created for it. Note that you will not be
able to delete your own operator.
2 Click Operators in the vertical menu.
3 On the Operators page, click the name of the operator you wish to delete.
4 On the Operator details page, click Delete.

The Delete button is also present on all of the other pages under the operator prefer-
ences.
5 If the operator has no child entities of any kind, you will see a message confirming
the successful deletion of the operator.
If any of the following types child entities are associated with the operator, you must
delete them before you are able to delete the operator entity:
• Operators
• Subscribers
• Subscriber types
• MMS applications
• Corporations
• User groups and accounts
38 Id:0900d80580428e98 DN70274664
Issue 5-0
Operating Guide Managing subscriber types
4 Managing subscriber types
4.1 Overview of subscriber types

As illustrated in the Data model in the Technical Reference document, each subscriber
in the Nokia Siemens Networks Profile Server (NPS) must belong to a subscriber type.
Subscriber type is in the profile resolution hierarchy between the subscriber and the
operator. Any service parameter which is not defined for a subscriber is taken from the
subscriber's subscriber type, if defined there. The operator's service default is used only
if the parameter is not defined for the subscriber or the subscriber type.
Note that it is never mandatory to define service profiles on the subscriber type and
operator levels. You should only do this if it avoids the need to provision the same data
for a large number of subscribers (potentially millions). Taking advantage of the profile
resolution hierarchy when possible can significantly increase the performance of the
NPS system.
Subscriber types are operator specific. However, their names must be unique in Profile
Server; there cannot be two subscriber types with the same name, even for different
operators.
AGW Profile NBG Profile VoIP Profile SMSC Profile MMS Profile
Operator Subscriber Type Subscriber MMS Application
CA Profile GGSN Profile TA Profile Presence Profile NTMS Profile
Figure 14 Entities and services
g Subscriber types may have the following service profiles:

• MMS service
• DLS service
• AGW service
• GGSN service
• TA service
• VoIP service
The DLS and AGW service profiles for the subscriber type cannot be edited using the
Administration User Interface (AUI).
For instructions on how to create a subscriber type, see section Creating a subscriber
type.
DN70274664 Id:0900d8058052d39e 39
Issue 5-0
Managing subscriber types Operating Guide
For instructions on how to manage existing subscriber types, see section Modifying or
deleting a subscriber type.
40 Id:0900d8058052d39e DN70274664
Issue 5-0
Operating Guide
4.2 Creating a subscriber type

Purpose
In Nokia Siemens Networks Profile Server (NPS), every subscriber must be associated
with a subscriber type. Follow this procedure when creating subscriber types for opera-
tors.
Steps
1 Log in AUI as a user with access to the Subscriber types resource.

If you log in as an operator-specific user, you can only create subscriber types for that
particular operator, and for any operators that are subordinate to the operator (sub-
VOs).
2 Click Subscriber types in the vertical menu bar.
3 Click New.
4 Select an operator for which you wish to create a subscriber type.
5 Enter a name and description for the subscriber type.

g The name of the subscriber type must be unique among the subscriber types in the
NPS database.
Figure 15 AUI - New subscriber type
6 Click Create.
After the subscriber type has been created, continue by setting the service profile
settings according to section Modifying or deleting a subscriber type.
DN70274664 Id:0900d8058052d3b4 41
Issue 5-0
Operating Guide
4.3 Modifying a subscriber type
4.3.1 Selecting the subscriber type

1. Log in to the AUI as a user with access to the Subscriber types & Additional
parameters resource. Note that operator-specific users only have access to their
own operator's subscriber types, and to the subscriber types of any operators that
are subordinate to their operator (sub-VOs).
2. Click Subscriber types in the vertical menu. The Subscriber types page opens.
3. You see a list of the subscriber types for that operator. Click the name of a sub-
scriber type to select it.
Figure 16 AUI - subscriber type selection

The following sections present the data which is available for the operator by clicking the
tabs on the horizontal navigation bar. If you change any data, remember to click Update
to save the changes.
4.3.2 Subscriber type - General

This page contains the following fields:
• Operator: The operator that owns the subscriber type. Cannot be changed.
• Name: The name of the subscriber type. Must be unique within NPS.
• Description: A description of the subscriber type. The description text is treated as
a string with no special limitations.
• Advertising enabled: Allows advertising messages to be sent. When advertising
has been enabled, messages with advertising content can be sent to the subscribers
belonging to this subscriber type. However, if the NPS targeted advertising support
feature has been disabled for the subscriber, messages will not be sent. For more
information on this feature, see NPS targeted advertising support in the Product
Description.
42 Id:0900d8058052d3bc DN70274664
Issue 5-0
Operating Guide
• Interests - List of interests that will be used as a default setting for the subscribers
belonging to this subscriber type if interests have not been defined on the subscriber
level.
g
Figure 17 Subscriber type - General
4.3.3 Subscriber type - MMS preferences

This page contains the MMS service profile of the subscriber type. If a subscriber does
not define a value for an MMS profile parameter, the value from the subscriber type
profile is used instead. For more information on profile resolution, see section Profile
resolution in the Technical Reference document.
• General
• Forwarding
• CC rules
• MO barring
• MT barring
DN70274664 Id:0900d8058052d3bc 43
Issue 5-0
Operating Guide
The content of the categories is the same as in the MMS service profile of a subscriber.
For more information on the fields and their meaning, refer to section Subscriber - MMS
Preferences.
4.3.4 Subscriber type - GGSN preferences

This page contains the GGSN service profile of the subscriber type. These settings and
access points are used if there is no GGSN service profile content in the profile of the
subscriber. If any parameters or access points are defined in the subscriber's profile, the
profile of the subscriber type is not noted at all.
The fields on this page, and the creation of the access points, are the same as in the
GGSN service profile of a subscriber. For more information, refer to section Subscriber
- GGSN Preferences.
4.3.5 Subscriber type - TA preferences

The TA preferences page is used to create and manage the rule set selectors in the
subscriber type's TA profile. These rule set selectors are used if there are no rule set
selectors defined in the TA service profile of the subscriber. If any rule set selectors are
defined in the TA service profile of the subscriber, the rule set selectors in the TA profile
of the subscriber type are not noted at all.
The page opens a page which displays the list of existing rule set selectors for this sub-
scriber type. Clicking the name of a rule set selector opens it for editing, and clicking the
New button opens the page for creating a new rule set selector. The rule set selectors
are created and edited in the same way as in the subscriber's TA service profile. For
more information, see section Subscriber - TA preferences.
4.3.6 Subscriber type - VoIP Server preferences

This page contains the VoIP service profile of the subscriber type. Only three parame-
ters can be defined on the subscriber type level; Group Profile ID, Location ID and
Authentication Profile ID. If the parameters are not defined in the subscriber's VoIP
service profile, the values from the subscriber type or operator profile are used.
For more information on the fields and their meaning, refer to section Subscriber - VoIP
Preferences.
44 Id:0900d8058052d3bc DN70274664
Issue 5-0
Operating Guide
4.4 Deleting a subscriber type

Purpose
Follow this procedure when deleting subscriber types. Remember that if a subscriber
type has subscribers associated with it (any subscribers have been defined as being of
that subscriber type), the type cannot be deleted.
Steps
1 Log in AUI as a user with access to the Subscriber types & Additional parameters
resource.
If you log in as an operator-specific user, you can only delete subscriber types that
belong to that particular operator, or any subordinate operator (sub-VO) that has been
defined for the operator.
2 Click Subscriber types in the vertical menu bar.
3 Select an operator and click Search.
4 The result list will show all subscriber types for the selected operator.
Figure 18 AUI - subscriber type selection
5 To delete a subscriber type, select the corresponding check box and click Delete.
You can only delete a subscriber type if there are no subscribers associated with
it.
You can also delete the current subscriber type by clicking the Delete button which is
present on all pages under the subscriber type.
DN70274664 Id:0900d8058052d3cb 45
Issue 5-0
Managing subscribers Operating Guide
5 Managing subscribers
5.1 Overview of subscriber management

Nokia Siemens Networks Profile Server (NPS) provides several interfaces for managing
the subscribers and their profiles in the database. The bulk of the operations on sub-
scribers should naturally be performed using the various data provisioning interfaces,
but the Administration User Interface (AUI) is convenient for infrequent manual sub-
scriber management tasks.
Subscriptions associate the subscribers with the services or service groups that they
want to use. Each subscription is associated with either one service or one service
group. Subscriptions have a specific validity period, which controls subscription expira-
tion. Subscriptions also have a status which can be “Enabled” or “Disabled”. Addition-
ally, subscriptions can have subscription-specific attributes, which override any service-
specific default attributes given for a service group or individual service.
Particularly the creation and editing of template subscribers (which are treated like
normal subscribers) is convenient and intuitive using the AUI.
For instructions on how to manage subscribers in AUI, see the following sections:
• Creating a subscriber
• Modifying a subscriber
• Deleting a subscriber
For instructions on how to create subscriptions to MMS services or service groups, see
section Subscriber - MMS preferences.
For instructions on how to create subscriptions to NBG services or service groups, see
section Subscriber - NBG preferences.
46 Id:0900d80580528e70 DN70274664
Issue 5-0
Operating Guide
5.2 Creating a subscriber

Purpose
Follow this procedure to create a new subscriber in the AUI.
Steps
1 Log in to AUI as a user with access to the Subscribers & Additional parameters
resource.
If you log in as an operator-specific user, you can only create subscribers for that par-
ticular operator.
2 Click Subscribers in the vertical menu.

The Subscribers page opens.
Figure 19 AUI - Subscribers page
3 Click New.
The New subscriber page opens.
DN70274664 Id:0900d8058052e78e 47
Issue 5-0
Operating Guide
Figure 20 AUI - New subscriber page
4 Enter the data for the new subscriber, and click Create.
MSISDN/MDN, Operator and Subscriber type are mandatory.
g If the IMSI/MSISDN range validation feature is enabled, the creation may fail if
MSISDN/MDN or IMSI is in conflict with resolution rules of the selected operator. For
more information on range validation, see section IMSI/MSISDN range validation in
provisioning.
5 The subscriber has now been created.

After creating a subscriber, the Subscriber - personal information page opens. This
page, and the other pages for the subscriber data, are described in section Modifying a
subscriber.
48 Id:0900d8058052e78e DN70274664
Issue 5-0
Operating Guide
5.3 Modifying a subscriber

Follow the instructions in this section when modifying the personal data and service
settings of a subscriber in the AUI. Remember to commit the changes by clicking the
Update button after making changes on a page.
5.3.1 Wildcards and references

Some parameter values in the subscriber's profiles (for example, email addresses in the
MMS service profile) may contain a reference to some other parameter in the sub-
scriber's profile. For more information on how to make use of these references, see
section Using reference parameters in the Technical Reference document.
It is also possible to use the wildcards asterisk "*" and question mark "?" in some data
fields. Such fields include, for example, barring addresses in the MMS service profile.
If used, the asterisk must always be the last character. There may be only one asterisk.
In addition to the asterisk, the pattern may optionally contain one or several question
marks that match to single characters in that particular position. For example: 35850*,
44530??*.
g The allowed wildcard use for email addresses is slightly different. The allowed
wildcard is asterisk "*". The email pattern contains two parts: <user>@<domain>.
The user part <user> may either be literally the user part, or an asterisk that
matches to all users for that domain. The domain part <domain> may contain from
two to several domains, separated by a dot “.”. The domains can be literal domains
or asterisks. For example:
*@*.com
*@operator.com
*@*
5.3.2 Selecting a subscriber

1. Log in to AUI as a user with access to the Subscribers & Additional parameters
resource. If you log in as an operator-specific user, you can only modify the sub-
scribers of that particular operator, and any subordinate operators (sub-VOs) that
have been defined for that operator.
2. Click Subscribers in the vertical menu. The Subscribers page opens.
3. Search for the subscriber you wish to modify. You can limit the search by subscriber
type and operator.
Select the desired identity type, and enter a search string in the field. If you wish to
see more than 10 results per page, select the Results per page accordingly. Click
the Search button to perform the search.
You can use wildcards "*" (asterisk) and "?" (question mark) in your searches.
Wildcard searches for large databases may take some time.
The subscriber identity types by which you can search are:
• MSISDN/MDN
• IMSI
• Last name
• Email address
• IP address
DN70274664 Id:0900d80580525c5b 49
Issue 5-0
Operating Guide
• CCB ID
• SIP URI
Figure 21 AUI - Subscribers page with result list

4. Select the subscriber you wish to edit by clicking on the name in the results list.
5.3.3 Subscriber - personal information

The Subscriber - personal information page opens. This page contains basic sub-
scriber information which is self-explanatory.
You can access the other pages for this subscriber by clicking the links on the horizontal
menu bar that has appeared.
50 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
Figure 22 AUI - Subscriber personal information page
5.3.4 Subscriber - identities

On this page you can add or modify the subscriber's identities:
• MSISDN/MDN: cannot be changed.
• IMSI
• IP address
• Email address
• Alias
• CCB ID
DN70274664 Id:0900d80580525c5b 51
Issue 5-0
Operating Guide
Figure 23 AUI - Subscriber - identities page
5.3.5 Subscriber - subscription

On this page you can modify settings related to the subscriber's subscription:
• Operator: The operator of the subscriber. If you are logged in as a non operator-
specific user, you can transfer the subscriber to a different operator. Note that this
also affects the subscriber type.
• Subscriber type: The subscriber type of this subscriber.
• Corporation: The corporation entity that the subscriber belongs to. For the short
number feature to work, the originator and recipient must be assigned to the same
corporation.
• Services flags: If these checkboxes are set, subscriber's profiles to the correspond-
ing services are enabled. When a new subscriber is created, the following flags are
enabled by default, even if the subscriber's operator does not have the correspond-
ing services enabled:
• MMS enabled
• AGW enabled
• DLS enabled
• Presence enabled
• GGSN enabled
• CA enabled
• TA enabled
• VoIP enabled
This means that the subscribers can have profiles to these services. However, the
profiles cannot be used through the profile fetch interfaces if the subscriber's
operator does not have the services enabled.
The Advertising enabled flag is disabled by default and must be enabled before
the subscriber is able to receive messages with advertising content.
• Presence used: If set, the subscriber has used Presence services at least once.
• WAP push capability: The WAP push capability of the subscriber, selectable from
the drop-down menu.
• Terminal type: String which identifies the type of the subscriber's terminal.
• Prepaid: If set, the subscriber is prepaid. If not set, the subscriber is postpaid.
52 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
• Intercepted: If set, the events related to this subscriber are intercepted. For more
information, see section Creating transaction log files.
• Barred: If set, the subscriber is barred from all profile fetch interfaces.
• SAIF enabled: If set, the subscriber is allowed to use the self-administration inter-
faces.
• SAIF user name: Subscriber's username for the Self-Administration Interface.
• SAIF password: Click the Change link to change the subscriber's SAIF password.
Figure 24 AUI - Subscriber's subscription page
5.3.6 Subscriber - MMS preferences

nine categories. To move from one category to another, click the name of the category
DN70274664 Id:0900d80580525c5b 53
Issue 5-0
Operating Guide

• General
• Forwarding
• CC rules
• MO barring
• MT barring
• Services
The settings on the operator's categories are always hidden from the subscriber, for
example when logged in to a self-administration interface. The operator settings contain
barrings, carbon copy addresses, etc. that the subscriber should not see.
MMS general parameters
Figure 25 Subscriber - MMS general parameters

The MMS general parameters category includes the following fields:
• Terminal capability: The MMS capability of the subscriber's terminal. Possible
values are MMS capable, MMS video capable, Not MMS capable, and
Unknown.
• Content adaptation: The content adaptation value for this subscriber. Possible
values are Allowed, Not allowed, and Unknown.
• Hide phone number: Set this checkbox to hide the phone number from the receiv-
ers of an MM when the current subscriber is the originator.
MMS forwarding rules

The MMS forwarding rules define when a MM is forwarded to the specified address or
addresses.
g The forwarding address types IMSI and MMS application ID are hidden in the
AUI because the Nokia Siemens Networks MMS Center does not support them.
Even though it is possible to set these address types for forwarding addresses
through the data provisioning interfaces (for example, the Profile Interface), it should
not be done as the correct operation of the MMS Center cannot be guaranteed.
If IMSI or MMS application ID forwarding addresses are stored in the database,
the address type will be replaced with MSISDN/MDN when shown in the AUI. If you
click Update, the address type will change into MSISDN/MDN in the database.
54 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
Figure 26 AUI - Subscriber's MMS profile - MMS forwarding rules section

The MMS forwarding rules category includes the following settings:
• Activate MMS forwarding: This checkbox is the master switch for all forwarding
settings on the page. If it is not checked, none of the specified forwarding rules are
used.
• When receiving from This checkbox enables the following forwarding options:
• a specific originator: You can define an address where the MM is forwarded
("To:") when it is received from a particular originator ("From:"). The allowed
address types are MSISDN/MDN and Email.
You can add new address pairs by clicking the Add button.
• the list of originators: You can define an address where the MM is forwarded
("To:") when it is received from particular originators ("From:"). The allowed
address types are MSISDN/MDN and Email.
You can add new addresses to the originator list by clicking the Add button.
• when roaming: This checkbox enables forwarding based on the roaming status of
the subscriber. When set, the MM is forwarded to the associated address ("To:")
when the subscriber is roaming.
• if larger than ___ kb: This checkbox enables forwarding based on the size of the
MM. When set, the MM is forwarded to the associated address ("To:") when the size
of the MM exceeds the set limit (in kilobytes). If the limit is set at zero, all messages
are forwarded regardless of the size (if the checkbox is set).
DN70274664 Id:0900d80580525c5b 55
Issue 5-0
Operating Guide
• if message class is of type: These checkboxes enable forwarding based on the

message class. When set, the MM is forwarded to the associated address ("To:") if
the type of the message corresponds to the selected types. The types are:
• Personal
• Advertisement
• Information
• Auto
• if any of the message class, message size or roaming conditions above apply:
This field defines a forwarding address ("To:") where the MM is forwarded if any of
the roaming, size or message class rules match.
CC rules
The MMS carbon copy (CC) rules define when a copy of an MM is sent to the specified
address or addresses. Barring rules are resolved separately for the CC addresses. If a
CC address is barred, a copy of the MM is not sent to it, even if the MM is delivered to
the original receiver.
g The CC address types IMSI and MMS application ID are hidden in the AUI
because the Nokia Siemens Networks MMS Center does not support them. Even
though it is possible to set these address types for CC addresses through the data
provisioning interfaces (for example, the Profile Interface), it should not be done as
the correct operation of the MMS Center cannot be guaranteed.
If IMSI or MMS application ID CC addresses are stored in the database, the
address type will be replaced with MSISDN/MDN when shown in the AUI. If you click
Update, the address type will change into MSISDN/MDN in the database.
Figure 27 AUI - Subscriber's MMS profile - CC rules

The CC rules category includes the following fields:
• Outgoing MMS to: When this checkbox is checked, a copy of all MMS sent by the
subscriber is sent to the specified address. Click the Add button to add a new
address field.
• Incoming MMS to: When this checkbox is checked, a copy of all MMS that are sent
to this subscriber is sent to the specified address.
• Incoming MMS while roaming to: When this checkbox is checked, a copy of all
incoming MMS that were received while the subscriber is roaming is sent to the
specified address.
• Content-adaptation MMS to: When this checkbox is checked, a copy of all content
adapted MMS is sent to the specified address.
56 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
MO barring
The MMS Mobile Originated (MO) barring category defines the barring rules for MMS
sent by the subscriber.
g The barring address type IMSI is hidden in the AUI because the NPS does not cur-
rently implement it. Even though it is possible to set this address type for barring
addresses through the data provisioning interfaces (for example, the Profile Inter-
face), it should not be done as the correct operation of the MMS Center cannot be
guaranteed.
If an IMSI barring address is stored in the database, the address type will be
replaced with MSISDN/MDN when shown in the AUI. If you click Update, the address
type will change into MSISDN/MDN in the database.
Figure 28 AUI - Subscriber's MMS profile - MO barring

The MO barring rules category includes the following fields:
• Activate barring when sending: This checkbox is the master switch for MO
barring. If it is not set, none of the specified MO barring rules are used.
• Bar sending to all destinations: When this option is selected, the subscriber is
completely barred from sending MMS.
• Bar sending with the following conditions: When this option is selected, the
detailed barring options below it are enabled.
• Bar sending to: The subscriber is barred from sending MMS to the specified
addresses. The allowed address types are MSISDN/MDN, Email and MMS
application ID. Click the Add button to add a new address field.
• when roaming: When this checkbox is set, the subscriber is barred from sending
MMS when roaming.
DN70274664 Id:0900d80580525c5b 57
Issue 5-0
Operating Guide
• if larger than ___ kb: This checkbox enables barring based on the size of the MM.
When set, the sending of the MM is barred when the size of the MM exceeds the set
limit (in kilobytes). If the limit is set at zero, all messages are barred regardless of
the size (if the checkbox is set).
• if message class is of type: These checkboxes enable barring based on the
message class. When set, the MM is barred if the type of the message corresponds
to the selected types. The types are:
• Personal
• Advertisement
• Information
• Auto
• if content type is one of these: These fields allow you to input MMS content types
that the subscriber is barred from sending. The content types are defined as HTTP
content types as they are specified in the MIME standard (see RFC 2045 and RFC
2046).
The content type names may be literal, such as text/html, or use the asterisk "*"
as a wildcard, as in video/*. In the latter case the barring may bar several different
content types matching to the wildcard rule. Barring rules * and */* always match
to every possible content type. Barring rule Text/* bars only content types starting
with "text", for instance these: text, text/HTML and
TEXT/Calendar.Gregorian (case insensitive comparison). The barring rules
can also match only a specific subtypes for a certain content type, for example
text/calendar.* bars only content type TEXT/Calendar.Gregorian from
the previous example. Barring rules can also be in the format */mpeg, in which case
any type having the sub type "mpeg" are barred.
The following three fields are whitelist barrings, which means that the other barrings
above (which are blacklist barrings) take precedence when resolving the barring status:
• Allow sending to all destinations: When this option is selected, the subscriber is
allowed to send MMS to all receivers.
• Only to: The subscriber is allowed to send MMS only to the specified addresses.
• Allow sending if content type is any of these: The subscriber is allowed to send
MMS only if the message is of the specified content type. The content types are
specified in the same way as for the blacklist content barring above.
MT barring
The MMS Mobile Terminated (MT) barring category defines the barring rules for MMS
received by the subscriber.
g The barring address type IMSI is hidden in the AUI because the NPS does not cur-
rently implement it. However, it is possible to set this address types for barring
addresses through the data provisioning interfaces (for example, the Profile Inter-
face).
If an IMSI barring address is stored in the database, the address type will be
replaced with MSISDN/MDN when shown in the AUI. If you click Update, the address
type will change into MSISDN/MDN in the database.
58 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
Figure 29 AUI - Subscriber's MMS profile - MT barring

The MT barring rules category includes the following fields:
• Activate barring when receiving: This checkbox is the master switch for MT
barring. If it is not set, none of the specified MT barring rules are used.
• Bar receiving from all sources: When this option is selected, the subscriber is
completely barred from receiving MMS.
• Bar receiving with the following conditions: When this option is selected, the
detailed barring options below it are enabled.
• Bar receiving from: The subscriber is barred from receiving MMS from the speci-
fied addresses. The allowed address types are MSISDN/MDN, Email and MMS
application ID. Click the Add button to add a new address field.
• when roaming: When this checkbox is set, the subscriber is barred from receiving
MMS when roaming.
• bar when roaming and sender is application: When this check box is set, the
roaming subscriber is barred from receiving MMS sent by any application.
• bar when roaming and sender is subscriber: When this check box is set, the
roaming subscriber is barred from receiving MMS sent by any subscriber.
• if larger than ___ kb: This checkbox enables barring based on the size of the MM.
When set, the receiving of the MM is barred when the size of the MM exceeds the
set limit (in kilobytes). If the limit is set at zero, all messages are barred regardless
of the size (if the checkbox is set).
• if message class is of type: These checkboxes enable barring based on the
message class. When set, the MM is barred if the type of the message corresponds
to the selected types. The types are:
• Personal
• Advertisement
• Information
DN70274664 Id:0900d80580525c5b 59
Issue 5-0
Operating Guide
• Auto
• if content type is one of these: These fields allow you to input MMS content types
that the subscriber is barred from receiving. The content types are defined as HTTP
content types as they are specified in the MIME standard (see RFC 2045 and RFC
2046).
The content type names may be literal, such as text/html, or use the asterisk "*"
as a wildcard, as in video/*. In the latter case the barring may bar several different
content types matching to the wildcard rule. Barring rules * and */* always match
to every possible content type. Barring rule Text/* bars only content types starting
with "text", for instance these: text, text/HTML and
TEXT/Calendar.Gregorian (case insensitive comparison). The barring rules
can also match only a specific subtypes for a certain content type, for example
text/calendar.* bars only content type TEXT/Calendar.Gregorian from
the previous example. Barring rules can also be in the format */mpeg, in which case
any type having the sub type "mpeg" are barred.
The following three fields are whitelist barrings, which means that the other barrings
above (which are blacklist barrings) take precedence when resolving the barring status:
• Allow receiving from all sources: When this option is selected, the subscriber is
allowed to receive MMS from all sources.
• Only from: The subscriber is allowed to receive MMS only from the specified
addresses.
• Allow receiving if content type is any of these: The subscriber is allowed to
receive MMS only if the message is of the specified content type. The content types
are specified in the same way as for the blacklist content barring above.
Operator's CC rules
The Operator's MMS carbon copy (CC) rules duplicate some of the settings in the basic
CC rules category. The difference is that the settings in the operator's categories
override those of the subscriber, and are always hidden from the subscriber, for example
when logged in to a self-administration interface.
Figure 30 AUI - Subscriber's MMS profile - Operator's CC rules

The Operator's CC rules category includes the following fields:
• Outgoing MMS to: When this checkbox is checked, a copy of all MMS sent by the
subscriber is sent to the specified address. Click the Add button to add a new
address field.
• Incoming MMS to: When this checkbox is checked, a copy of all MMS that are sent
to this subscriber is sent to the specified address.
60 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
Operator's MO barring
The Operator's MO barring rules duplicate the settings in the basic MO barring rules cat-
egory. The difference is that the settings in the operator's categories override those of
the subscriber, and are always hidden from the subscriber, for example when logged in
to a self-administration interface.
Figure 31 AUI - Subscriber's MMS profile - Operator's MMS MO barring
Operator's MT barring
The Operator's MT barring rules duplicate the settings in the basic MT barring rules cat-
egory. The difference is that the settings in the operator's categories override those of
the subscriber, and are always hidden from the subscriber, for example when logged in
to a self-administration interface.
DN70274664 Id:0900d80580525c5b 61
Issue 5-0
Operating Guide
Figure 32 AUI - Subscriber's MMS profile - Operator's MT barring
Services
The service and service group subscriptions allow a subscriber to subscribe to MMS
services or service groups. This, together with the advertising enabled flag, enables
advertisements to be sent to a subscriber based on these services. The page lists all
MMS Service Groups and Services which have been configured using the Services con-
figuration page. When a checkbox next to the name of the service is checked the sub-
scriptions begin and end dates are displayed together with the status of the subscription.
Figure 33 AUI - Subscriber's MMS profile - Services
5.3.7 Subscriber - AGW preferences

On this page, you can set the Class of Service (COS) value for the Application Gateway
(AGW) profile of this subscriber. To edit other parameters in the subscriber's AGW
service profile, you must use the AGW GUI.
62 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
Figure 34 AUI - Subscriber AGW preferences page
5.3.8 Subscriber - DLS preferences

On this page, you can set the following settings in the subscriber's Delivery Server
profile:
• Adult content enabled: Set this flag to enable the Adult content group
• Premium content enabled: Set this flag to enable the Premium content group
• Barred: Set this flag to bar the subscriber from using the DLS service.
• DLS user name: Subscriber's username for DLS.
• DLS password: Change the subscriber's DLS password by clicking on the Change
link.
Figure 35 AUI - Subscriber DLS preferences page
5.3.9 Subscriber - Presence preferences

On this page, you can set the following settings in the subscriber's Presence Server
profile:
• Wireless Village user ID: The Wireless Village ID of the subscriber.
• Wireless Village password: The Wireless Village password of the subscriber. Click
the Change link to change it.
DN70274664 Id:0900d80580525c5b 63
Issue 5-0
Operating Guide
• Subscription limit: Defines how many Presence Server subscriptions a subscriber

can have (subscriptions to the presence data of other subscribers). The value
cannot be less than zero.
• Creation date: The date when the Presence settings were created for this sub-
scriber. The date format is format YYYY.MM.DD hh:mm:ss
Figure 36 AUI - Subscriber Presence preferences page
5.3.10 Subscriber - GGSN preferences

g The subscriber must have an IMSI before any GGSN preferences can be set.
On this page, you can set the following settings in the subscriber's Gateway GPRS
Support Node profile:
• Charging characteristics: Subscriber's charging characteristics.
• Trec ID: Defines the base TREC for PDP context. Allowed values are in range 0-10.
• OCS ID, value 1: Id of the OCS server. Must be an integer in the range 1-65536.
• OCS ID, value 2: Id of the OCS server. Must be an integer in the range 1-65536.
64 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
Figure 37 AUI - Subscriber GGSN preferences
5.3.10.1 Subscriber - GGSN preferences - Access points

The Access points tab on the Subscriber - GGSN preferences page opens a page
which displays the list of existing access points for this subscriber. Click the name of an
access point to edit it, or click the New button to create one.
Figure 38 AUI - Subscriber - GGSN preferences - Access points

When creating a new access point, you must first enter a Name for it. The access point
name must be unique for the subscriber (subscriber cannot have multiple access points
with the same name).
After you have given a name to the access point, you can add Services to the access
point. Click the Services tab to display the current list of services attached to this access
point, and click New to create a new one.
When creating a new service, you must fill in the following fields:
• Name: The name of the service. Must be unique within the access point.
DN70274664 Id:0900d80580525c5b 65
Issue 5-0
Operating Guide
• Activation status: The activation status of the service.

g Each access point must have at least one service with the activation status 2,
Default.
• Wallet ID: Wallet identifier for charging. Allowed values are in range 1-127.
• Wallet charging type: Service-specific wallet charging type.
When viewing the service after it has been created, some additional fields will be shown:
• Activation date: This is a timestamp maintained by the NPS, displaying the date
when the service was last activated (Activation status set to 0, 2, or 4).
• Deactivation date: This is a timestamp maintained by the NPS, displaying the date
when the service was last deactivated (Activation status set to 1 or 3).
• ID and authentication: String containing a username and a password, separated
by a colon. Used for service activation; services that don’t need authentication are
directly accessible.
Figure 39 AUI - Subscriber - GGSN preferences - Access points - service
5.3.11 Subscriber - CA preferences

g The subscriber must have an IMSI before any CA preferences can be set.
This page contains the following settings in the subscriber's Content Analyzer service
profile:
• ITA subscription ID: This is an unique ID for the content subscription. It is automat-
ically generated by the NPS, and cannot be changed. The abbreviation "ITA" refers
to the old name of the Content Analyzer network element.
• Billing type: The billing type for the subscriber.
• Currency: Id of the subscriber’s preferred currency. The format is according to
alphabetic ISO 4217, e.g. ‘GBP’ for UK Pound.
• ITA active: If this checkbox is checked, the advice-of-charge dialog is shown to the
subscriber.
66 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
g Do not define additional parameters which have identical names to other param-
eters which already exist.
Figure 40 AUI - Subscriber - CA preferences
5.3.12 Subscriber - CA preferences - Content subscriptions

The Subscriptions tab on the Subscriber - CA preferences page opens a page which
displays the list of existing content subscriptions for this subscriber. Click the ID of a sub-
scription to edit it, or click the New button to create one.
When creating or editing a content subscription, the following data must be entered:
• Content Service ID: The ID of the content service. This ID cannot be freely entered,
it must be selected from a drop-down list which presents all currently valid content
service IDs. NPS retrieves the IDs from the ISD database; for more information, see
section Setting up the connection to ISD in the Integration Guide.
g If the content service IDs are unavailable, you will receive a notification that the
CA service data poller should be configured. Please follow the instructions in
section Setting up the connection to ISD in the Integration Guide. Alternatively,
you can provision the IDs manually as described in section Using the ISD
service data tool in the Administration Guide.
• Starting date and Ending date: The starting and ending date of the content sub-
scription. You must enter the dates in format YYYY.MM.DD hh:mm:ss. When
entering the dates, remember that they are always assumed to be in UTC (Zulu)
time.
DN70274664 Id:0900d80580525c5b 67
Issue 5-0
Operating Guide
Figure 41 Subscriber - CA preferences - New content subscription
5.3.13 Subscriber - TA preferences

g The subscriber must have an IMSI before any TA preferences can be set.
This page contains a list of the rule set selectors that have been stored for this sub-
scriber. Click on the Rule Set ID of a rule set selector to edit it, or click the New button
to create one.
When creating or editing a rule set selector, the following data can be entered:
• Rule Set ID: This is the only mandatory field for a rule set selector. Enter the ID of
the rule set (stored on the TA) where this selector points.
• Criteria applied to select the rule set ID above
Enter the criteria which are used to match the request from the TA to the rule set ID.
You may leave any or all of the following information empty:
• Access point name: The name of the access point that matches this rule set
selector.
• Roaming: The roaming status of the subscriber.
• Charging characteristics: The charging characteristics string that matches this
rule set selector.
• Access type: The access type of the subscriber.
• IMEI(SV): The terminal's International Mobile station Equipment Identity and
Software Version (IMEISV) number in BCD encoding.
• MCC/MNC: The SGSN MCC/MNC number.
• Location: The 3GPP-User-Location-Info octet string in hexadecimal.
• Timezone: The 3GPP-MS-TimeZone two-octet string in hexadecimal. The first
octet defines offset from universal time to local time in number of 15 minute
steps, the second whether daylight saving time is in use.
• Parameters returned to TA
Select the values for the response that the TA will receive:
• Billing type: The billing type of the subscriber.
• Prepaid server: The IP address of the prepaid server.
• Mobile IP Secret: The subscriber's authentication secret for mobile IP.
68 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
Figure 42 AUI - Subscriber - TA preferences - New rule set selector

In addition to creating rule set selectors for the subscriber, you can also store additional
parameter-value pairs in the subscriber's TA service profile. Click the Additional
parameters tab to display the list of currently defined additional parameters, and click
the Add button to enter a new parameter-value pair.
g Do not define additional parameters which have identical names to other parame-
ters which already exist.
5.3.14 Subscriber - NTMS preferences

On this page, you can enter the following information in the Nokia Siemens Networks
Terminal Management Server (NTMS) preferences of the subscriber:
• NTMS group: The NTMS provisioning group of the subscriber. You can assign or
change the group by selecting a new group from the drop-down menu. For instruc-
tions on how to manage the NTMS groups, see section Managing NTMS groups.
• Terminal model: The model of the subscriber's mobile terminal. You can assign or
change the model by selecting a new model from the drop-down menu. For instruc-
tions on how to manage terminal models, see section Managing terminal models.
• IMEI: The 15-digit International Mobile Equipment Identity (IMEI) code of the sub-
scriber's mobile terminal.
For more information on the NTMS support of the NPS, see section Overview of NTMS
support in the Integration Guide.
DN70274664 Id:0900d80580525c5b 69
Issue 5-0
Operating Guide
Figure 43 AUI - Subscriber - NTMS preferences
5.3.15 Subscriber - VoIP preferences

On this page, you can enter the following information in the Voice over IP (VoIP) prefer-
ences of the subscriber:
• SIP URI: The session initiation protocol (SIP) uniform resource identifier (URI) of the
subscriber. Must be unique in the NPS database.
A string of 1-99 characters with the format <userpart>@<domainpart>, where
the optional <userpart> is 1-34 characters and <domainpart> is 1-64 charac-
ters. If both parts exist, they must be separated by the at sign "@".
• VoIP Username: The subscriber's VoIP username, used in authentication.
• VoIP Password: The subscriber's VoIP password, used in authentication. Click the
Change link to change it.
• GroupProfileId: Group Profile Id for the subscriber. An integer between 0-299.
• CommonUri Flag: If set, the Common URI is applied.
• Common URI: The common SIP URI for the subscriber. This URI does not have to
be unique among subscribers.
• LocationId: Location Id for the subscriber. An integer between 0-999.
• Authentication Profile ID: The authentication profile ID of the subscriber. An
integer between 0-49.
• Presence Server ID: The Presence Server ID of the subscriber.
• Mwi Server ID: The MWI server ID of the subscribe.
• Common MSISDN: Defines an MSISDN which should be shown as a CLI when a
subscriber is calling, intiating a MESSAGE etc.
• CsIMSI: Defines a CS IMSI to which this SIP user is logically connected.
• CsIMSI Usage: Defines on feature basis whether to use the CS_IMSI or not.
• Additional Parameters: Click the Add button to enter a new parameter-value pair.
g Do not define additional parameters which have identical names to other param-
eters which already exist.
70 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
Figure 44 AUI - Subscriber - VoIP preferences
5.3.16 Subscriber – SMSC preferences

The SMSC profile of a subscriber contains references to the SMSC configuration data.
On this page you can enter the following information in the SMSC preferences of the
subscriber:
• Delivery Attributes Reference: The id of the Delivery Attributes configuration
profile that SMSC should apply for this user.
• Content Based Filtering Reference: The id of the Content Based Filtering config-
uration profile that SMSC should apply for this user.
• Incoming Capacity Allocation Reference: The id of the Incoming Capacity Alloca-
tion configuration profile that SMSC should apply for this user.
• Regional Barring Reference: The id of the Regional Barring configuration profile
that SMSC should apply for this user.
• Lawful Trace Reference: The id of the Lawful Trace configuration profile that
SMSC should apply for this user.
DN70274664 Id:0900d80580525c5b 71
Issue 5-0
Operating Guide
• Additional References: Name and id pairs of additional SMSC configuration

profiles that SMSC should apply for this user.
If the configuration profile '0 - Default' is selected, then SMSC takes in use the default
rule for that feature. To add more items to the configuration id lists of features, see
section Creating new SMSC configurations.
5.3.17 Subscriber – NBG preferences

On this page you can enter data for the new subscriptions to NBG services or service
groups. The page shows all the NBG service groups and services which have been con-
figured using the Services configuration page. When a checkbox next to the name of the
service is checked, the begin and end dates of the subscription are displayed together
with the status of the subscription. The URL for the subscriber’s home page is also
shown in Subscriber – NBG preferences. For the service group or service subscriptions,
Begin date, End date and Status are mandatory.
You can enter the following parameters:
• URL: URL for Home page redirection.
• Service group subscriptions: The name of the service group of the subscription.
• Service subscriptions: The name of the service of the subscription.
• Begin date: Indicates the date when this subscription becomes active. Format is
YYYYMMDD.
• End date: Indicates the date after which this subscription becomes inactive. Format
is YYYYMMDD.
• Status: Indicates the status of the subscription. It can be either Enabled or Disabled.
• Additional Parameters: Click the Add button to enter a new parameter-value pair.
g Additional attributes are a licensed feature. A license is needed to store and retrieve
attributes for services, service groups, and subscriptions.
72 Id:0900d80580525c5b DN70274664
Issue 5-0
Operating Guide
To modify default attributes, you must first deselect the Default box of that attribute.
After that it is possible to modify the attribute's value. It is only possible to delete a default
attribute at the level (either service or service group) where it was originally set.
Figure 45 AUI – Subscriber - NBG preferences page
DN70274664 Id:0900d80580525c5b 73
Issue 5-0
Operating Guide
5.4 Deleting a subscriber

Purpose
Follow this procedure to delete a subscriber using the AUI.
Steps
1 Log in AUI as a user with access to the Subscribers & Additional parameters
resource.
If you log in as an operator-specific user, you can only delete subscribers that belong to
that particular operator, and any subordinate operators (sub-VOs) that have been
created for it.
2 Click Subscribers in the vertical menu.

The Subscribers page opens.
3 Search for the subscriber you wish to delete.

Select the desired identity type, and enter a search string in the field. To change the
number of results that are shown on one page, select the Results per page accordingly.
Click Search.
You can use wildcards "*" (asterisk) and "?" (question mark) in your searches. Wildcard
searches for large databases may take some time.
The subscriber identity types by which you can search are:
• MSISDN/MDN
• IMSI
• Last name
• Email address
• IP address
• CCB ID
• SIP URI
74 Id:0900d80580543459 DN70274664
Issue 5-0
Operating Guide
Figure 46 AUI - Subscribers page with result list
4 Select the checkbox of the subscriber(s) you wish to delete, and click Delete.
DN70274664 Id:0900d80580543459 75
Issue 5-0
Managing services Operating Guide
6 Managing services
6.1 Overview of service management

To create and modify services, service groups, or subscriptions, you can use the Admin-
istration User Interface (AUI).
In this document, the term service refers to services which a given client of the Profile
Server offers to subscribers. For instance, the virus scanning function offered by the
Nokia Siemens Networks Browsing Gateway (NBG) is one of the services covered by
Subscription and Service Management Support.
Each service has a type and a name. The service type is used to group together
services which, for example, relate to the same Profile Server client (such as NBG). The
name is free-form text and it must be unique for all services of a certain service type.
Services also have a status which can be either “Enabled” or “Disabled”. It is also
possible to give default attributes for services.
Several services can be combined into service groups, which makes it easier to give
multiple subscribers access to the same set of services. Each service can belong to one
or several service groups. Service groups have the same parameters as services; type,
name and status. A service group can also hold default attributes for the services in the
group. This provides an easy way to set default attributes for a specific group of users.
The attributes of a service group override the default values given for the service.
For instructions on how to create services, see Creating NBG services and Creating
MMS services.
For instructions on how to create service groups, see Creating NBG service groups and
Creating MMS service groups.
76 Id:0900d8058054345c DN70274664
Issue 5-0
Operating Guide
6.2 Creating an NBG service

Purpose
Follow this procedure to create a new NBG service in the AUI. You can create a new
generic service in a similar manner on the Generic services page.
Steps
1 Log in to the AUI.
2 Select Services in the vertical menu. The NBG Services page opens:
Figure 47 AUI – NBG Services page
3 To create a new service, click New next to Services.

The Create NBG Services page opens.
Figure 48 AUI – Create NBG Services page
DN70274664 Id:0900d80580543464 77
Issue 5-0
Operating Guide
4 Enter the data for the new service, and click Create. Name and Status are manda-
tory.
On this page, you can enter the following parameters:
Parameter Example
Name Virus scan
Description Virus scan service
Status Enabled
You can also enter the following additional attributes:
Parameter Example
Name Heuristics
Type Enabled
attributes for services, service groups, and subscriptions
5 The data is shown on the AUI – NBG Service details page.
Figure 49 AUI – NBG Service details page
6 The service has now been created.
78 Id:0900d80580543464 DN70274664
Issue 5-0
Operating Guide
6.3 Creating an NBG service group

Purpose
Follow this procedure to create a new NBG service group in the AUI. You can also
create a new Generic service group in a similar manner on the Generic service group
pages.
Steps
2 Select Services in the vertical menu. The NBG Services page opens:
Figure 50 AUI – NBG Services page
3 To create a new service group, click New next to Service Groups.

The Create NBG Service group page opens.
DN70274664 Id:0900d80580543466 79
Issue 5-0
Operating Guide
Figure 51 AUI – Create NBG Service group page
4 Enter the data for the new service group, and click Create. Name and Status are
mandatory
Further information
Parameter Example
Name Virus scan
Status Enabled
You can also set the following member parameter:
Parameter Example
Name Heuristics
Type Enabled
5 The data appears on the AUI – NBG Service group details page.
If an attribute was added for the service, the default attribute Heuristics is shown in grey
and the Default box is selected. This indicates that the attribute and its value have been
defined as the default values for the Virus scan service on the Service level.
g To modify default attributes, you must first deselect the Default box of that attribute.
After that it is possible to modify the attribute's value. It is only possible to delete a
80 Id:0900d80580543466 DN70274664
Issue 5-0
Operating Guide
default attribute at the level (either service or service group) where it was originally
set.
Figure 52 AUI – NBG Service group details page
6 The service group has now been created.
DN70274664 Id:0900d80580543466 81
Issue 5-0
Operating Guide
6.4 Creating an MMS service

Purpose
Follow this procedure to create a new MMS service in the AUI.
Steps
1 Log into the AUI.
2 Select Services in the vertical menu. The MMS Services page opens:
Figure 53 AUI – MMS Services page
3 To create a new service, click New next to Services.

The Create MMS Services page opens.
Figure 54 AUI – Create MMS Services page
82 Id:0900d80580543468 DN70274664
Issue 5-0
Operating Guide
4 Enter the data for the new service, and click Create. Name and Status are manda-
tory.
Parameter Example
Name Virus scan
Status Enabled
You can also enter the following additional attributes:
Parameter Example
Name Heuristics
Type Enabled
attributes for services, service groups, and subscriptions
5 The data is shown on the AUI – MMS Service details page.
Figure 55 AUI – MMS Service details page
6 The service has now been created.
DN70274664 Id:0900d80580543468 83
Issue 5-0
Operating Guide
6.5 Creating an MMS service group

Purpose
Follow this procedure to create a new MMS service group in the AUI.
Steps
2 Select Services in the vertical menu. The MMS Services page opens:
Figure 56 AUI – MMS Services page
3 To create a new service group, click New next to Service Groups.

The Create MMS Service group page opens.
84 Id:0900d8058054346a DN70274664
Issue 5-0
Operating Guide
Figure 57 AUI – Create MMS Service group page
4 Enter the data for the new service group, and click Create. Name and Status are
mandatory
Further information
Parameter Example
Name Virus scan
Status Enabled
You can also set the following member parameter:
Parameter Example
Name Heuristics
Type Enabled
5 The data appears on the AUI – MMS Service group details page.
If an attribute was added for the service, the default attribute Heuristics is shown in grey
and the Default box is selected. This indicates that the attribute and its value have been
defined as the default values for the Virus scan service on the Service level.
g To modify default attributes, you must first deselect the Default box of that attribute.
After that it is possible to modify the attribute's value. It is only possible to delete a
DN70274664 Id:0900d8058054346a 85
Issue 5-0
Operating Guide
default attribute at the level (either service or service group) where it was originally
set.
Figure 58 AUI – MMS Service group details page
6 The service group has now been created.
86 Id:0900d8058054346a DN70274664
Issue 5-0
Operating Guide Managing corporations
7 Managing corporations
7.1 Overview of corporations and short number support

Short numbers are applied in many organizations to make the internal communication
easier. To support this, NPS has a short number feature which enables the originator of
an MMS message to send the message to the recipient by using a short number. The
feature has been implemented using operator-specific corporation entities. Corpora-
tions entities enable the operator to maintain lists of subscribers and short number asso-
ciations.
If the short number of the recipient is found from the corporation of the originator during
originator profile fetch, the recipient’s short number is replaced with the corresponding
MSISDN. After this the originator and recipient profile fetches operate normally. Short
numbers are unique only inside the corporation to which they belong; globally they are
not unique.
g Short numbers are not resolved between different corporations. This means that
subscribers that belong to different corporations cannot use short numbers to com-
municate with each other, even if they both belong to the same operator.
Also note that there are no structured relationships between corporations. It is not
possible to create a hierarchy of corporations that would enable subscribers in dif-
ferent corporations to communicate with each other using short numbers.
This feature is controlled by the NPS license. If the feature is not enabled, then the cor-
porate number resolution is not done even if the criteria for it would be met. In that case
the short number is treated as a normal MSISDN (or application number).
For instructions on managing the corporation entities, see the following sections:
• For instructions on creating a corporation, see section Creating a corporation.
• For instructions on adding short number associations or deleting a corporation, see
section Modifying or deleting a corporation.
• When using the AUI, the subscribers are assigned to corporations on the
Subscription page of the subscriber. For more information, see section Modifying
a subscriber.
7.1.1 Checklist for managing short numbers

For short numbers to work, the following conditions must be true:
• The corporate short number resolution must be enabled (it is enabled by default).
This is controlled by the property nap.core.mmsc.shortNumber.enabled in
the property file mmsc.properties. For more information, see section Configura-
tion files in the Parameter Reference document.
• The originator, recipient, and the corporation must all exist under the same operator
entity.
• The originator and receiver must be assigned to the same corporation. Note that a
subscriber can only belong to one corporation at a time.
• The short number has been mapped to the recipient's MSISDN/MDN in the corpo-
ration's profile.
DN70274664 Id:0900d80580543474 87
Issue 5-0
Managing corporations Operating Guide
• There must not be an MMS application entity that has the same application ID as the
short number. MMS application IDs are resolved before the short numbers, so the
MMS profile fetch will retrieve the MMS application's profile instead.
g Operator-specific users can only create, modify, and delete corporations that belong
to their own operator, and any subordinate operators (sub-VOs) they control. Non
operator-specific users can manage the corporation entities of all operators.
88 Id:0900d80580543474 DN70274664
Issue 5-0
Operating Guide
7.2 Creating a corporation

Purpose
To create a new corporation entity in the Nokia Siemens Networks Profile Server (NPS).
For more information on corporations, see section Overview of corporations and short
number support.
Before you start

You can only create new corporation entities if the short numbers feature is enabled by
the NPS license.
Steps
1 Log in to AUI as a user with access to the Corporations resource.
2 Click Corporations in the vertical menu.
3 On the Corporations page, click New. The New corporation page opens.
Figure 59 New corporation page
4 Enter a name for the new corporation.

Corporation ID is the unique string by which the corporation is recognized in the Profile
Server. The string may be up to 120 characters long, and may contain spaces. The fol-
lowing characters are not allowed:
• " (quote)
• ' (apostrophe)
• & (ampersand)
• < (less than)
• > (greater than)
• = (equals)
• + (plus)
• / (slash)
• \ (backslash)
• % (percentage sign)
• : (colon)
• ; (semicolon)
DN70274664 Id:0900d80580543479 89
Issue 5-0
Operating Guide
5 Select the operator for the corporation. You can only select those operators that
your user account has access to.
6 Enter a short description for the corporation.
7 Click Update to commit your changes.

Now go to section Modifying or deleting a corporation to continue configuring the corpo-
ration settings and the list of short number associations.
90 Id:0900d80580543479 DN70274664
Issue 5-0
Operating Guide
7.3 Modifying or deleting a corporation

Purpose
To modify or delete corporation entities. The corporation entities are usually modified to
maintain their list of short number associations.
Steps
1 Log in AUI as a user with access to the Corporations resource.

If you log in as an operator-specific user, you can only create and modify corporations
that belong to your operator, and any subordinate operators (sub-VOs) that have been
created for it.
2 Click Corporations in the vertical menu bar.
3 On the Corporations list, click the name of the corporation.
4 The Corporation details page opens.

• To delete the corporation, click Delete.
• To modify the corporation, edit the name and description of the corporation on this
page. Note that the corporation's operator is defined at creation and cannot be
edited later.
Figure 60 Corporation details
5 Clicking the Short numbers tab will open the Corporation - Short numbers page.
The Corporation - Short numbers page allows you to search and maintain the corpo-
rations's list of short number associations. You can search either by the short number
or the MSISDN/MDN.
DN70274664 Id:0900d8058054347b 91
Issue 5-0
Operating Guide
To create a new short number association, click the New button.

To delete the existing short number association, select its Delete checkbox in the search
results list, and click Delete.
Figure 61 Corporation - Short numbers
g Remember that in addition to creating a short number association, you must also
associate the subscriber with the corporation. In AUI, you can do this on the
Subscriber - Subscription page. For more information, see section Modifying a
subscriber.
92 Id:0900d8058054347b DN70274664
Issue 5-0
Operating Guide Managing MMS application profiles
8 Managing MMS application profiles

Purpose
The MMS application entities in Nokia Siemens Networks Profile Server (NPS) are
similar to subscriber entities. An MMS application is identified by its application ID, which
is used by the MMS Center to fetch its profile.
MMS application entities can have the same MMS service profile settings as a sub-
scriber. Also, MMS applications can be linked to distribution lists (DLs), which enable
MMS applications to push multimedia messages to a large number of subscribers with
a single sending action. For more information on DLs, see section Overview of distribu-
tion lists.
Follow the procedure below to manage MMS application profiles.
Steps
1 Log in to AUI as a user with access to the MMS applications resource.

If you log in using an operator-specific user account, you can only manage the MMS
application profiles for that operator.
2 Click MMS applications in the vertical menu bar.

The MMS applications page opens. On this page you can search for MMS applications
using wildcards asterisk "*" and question mark "?".
DN70274664 Id:0900d80580544d76 93
Issue 5-0
Managing MMS application profiles Operating Guide
Figure 62 AUI - MMS applications page with search results list
3 To delete an MMS application profile, select its checkbox in the results list and
click the Delete button.
4 To create a new MMS application profile, click New.

The New MMS application page opens.
94 Id:0900d80580544d76 DN70274664
Issue 5-0
Operating Guide Managing MMS application profiles
Figure 63 AUI - New MMS application page
5 Fill in the data for the new MMS application, and click Create.
• Operator : The operator to which this MMS application profile will belong.
• ID: The unique identifier for the MMS application. May contain numbers and letters,
length must be 1-20 characters.
• Description: Description for the MMS application. The description text is treated as
a string with no special limitations.
• MMS enabled: Set this checkbox if you wish to enable this MMS application to have
an MMS service profile. Also enables the application to use MMS distribution lists.
• Barred: Set this checkbox if you wish to totally bar this MMS application.
• Intercepted: Set this checkbox if you wish to enable intercept logging for this MMS
application.
• Validity start date: The date from which this MMS application is valid. The format
is YYYY.MM.DD hh:mm:ss.
• Validity end date: The date when the validity of this MMS application ends. The
format is YYYY.MM.DD hh:mm:ss.
• Maximum number of lists: The maximum number of distribution lists that may be
associated with this application.
• Resolved lists allowed: Set this checkbox if you want to allow this MMS application
to be associated with resolved lists (the personalised push feature).
DN70274664 Id:0900d80580544d76 95
Issue 5-0
Managing MMS application profiles Operating Guide
• Maximum size of non-resolved lists: The maximum number of members that may
belong to non-resolved distribution lists associated with this MMS application (per-
sonalised push not used).
• Maximum size of resolved lists: The maximum number of members that may
belong to resolved distribution lists associated with this MMS application (person-
alised push is used).
6 To modify the profile of an MMS application, click the name of the MMS applica-
tion in the search results list.
The MMS application details page opens. If you are continuing directly from MMS
application creation, you are already on that MMS application's details page.
7 On the MMS application details page, you can change all of the same items as
when creating the MMS application, except for the MMS application id.
If you are logged in as a non operator-specific user, you can also associate the MMS
application profile with another operator.
Click Update to commit your changes on this page.
8 Click the MMS link to display the MMS service profile settings for the application.
• General
• Forwarding
• CC rules
• MO barring
• MT barring
• Operator's MT barring
The settings in the operator categories are always hidden from the subscriber, for
example when logged in to a self-administration interface. The operator settings contain
barrings, carbon copy addresses, etc. that the subscriber should not see.
g An MMS application has exactly the same MMS service profile as a subscriber. For
more information on the fields and their meaning, refer to section Subscriber - MMS
Preferences.
When you are done modifying any page in the MMS application's profile, click Update
to commit your changes. If you switch pages before committing the changes, the
changes will be lost.
96 Id:0900d80580544d76 DN70274664
Issue 5-0
Operating Guide Distribution lists
9 Distribution lists
9.1 Overview of distribution lists

The Distribution lists for MMS Push feature of Nokia Siemens Networks Profile Server
(NPS) allows MMS applications to send multimedia messages to a predefined group of
end-users by initiating a single sending action. Distribution lists (DLs) may be of any
size, from a few members up to the maximum number of subscribers in NPS database.
A distribution list for MMS push is a list of addresses that can be either MSISDN/MDNs,
email addresses, or a mix of both. The addresses are validated as MSISDN/MDN or
email addresses, depending on the presence of "@" in the address. The size of a distri-
bution list is only limited by the supported size of the database in the used hardware con-
figuration, which means that you can create lists with millions of entries.
Due to the special usage and performance needs of the distribution lists, the DL
members are stored separately from the real subscriber profiles and there is no physical
link between these entities. Note that the order of the members inside a DL is not guar-
anteed in any way.
DLs and MMS applications are stored as separate entities. Their combination is the “ser-
vice” that the end user will get. Each defined MMS application – DL combination has
common information, for example the MMS application alias to be returned to MMS
Center when it fetches the DL information. This alias is shown to the end user as the
source of a service that was pushed to the user's mobile phone.
MMS APPLICATION DISTRIBUTION LIST
MMS application id List name

VoID MMS application id
Description APPLICATION ALIAS
VoID
Barring flag Description
MMS active flag MMS application alias
Delay (minutes)
Intercepted flag Barred flag
Delay (number of members)
Validity start date Validity start date
Content adaptation setting
Validity end date Validity end date
Barred flag
Maximum number of DLs Resolved flag
Resolved list allowed flag IMSI query flag
Maximum size of bulk list Prepaid flag
Maximum size of resolved list
Figure 64 DLs and MMS applications

MMS applications are always linked to exactly one Virtual Operator (VO), but DLs can
be either VO-specific or not. The management of the MMS applications and DLs is con-
trolled via user groups and access rights.
Operators can define common actions to be taken by the MMS Center for each list entry
when the MMs are processed. In NPS, the available common list attributes are:
• Delay: number of processed DL members after which the MMS Center will wait for
a set delay time before continuing with the DL processing
Content adaptation setting: Defines whether to allow or not allow content adaptation
for all DL members
• Barred flag: Restricts the access of MMS applications to the distribution list.
DN70274664 Id:0900d80580544d7e 97
Issue 5-0
Distribution lists Operating Guide
• Resolved flag: NPS resolves the individual receiver profiles for each DL member
that matches a subscriber profile in the database (personalised push).
When personalised push is not activated for a DL, the common profile of the DL is
applied for each list member. This means that no individual subscriber profiles are
requested for the listed MSISDN/MDNs or email addresses. The only receiver infor-
mation for MMS Center is just the plain MSISDN/MDNs or email addresses.
When the personalised push feature is activated, individual subscriber profile
fetches are initiated for DL members.With personalised push, the MMS Center
fetches the profiles for each DL member separately, and NPS attempts to resolve
the MMS receiver profile for each address. This way the personalised settings of
each end user are taken into use. The maximum size of DLs that can be used with
personalised push can be limited by the network operator, to prevent stalling the
MMS Center and the NPS due to excessive profile fetches.
g It is very important to specify a reasonable limit for the size of resolveable DLs.
Resolving DLs with millions of members will occupy both the NPS and the MMS
Center for several hours.
• IMSI query flag: MMS Center shall execute an IMSI query for each DL member.
• Prepaid flag: Defines that the balance of the DL members needs to be checked by
the MMS Center (e.g. using IACC) because they are prepaid.
The DL feature is supported by the NPS interfaces as follows:
• The MMS Center is the only pre-integrated network element that fetches DLs.
• The Profile Interface (PI) makes it possible for operator and MMS application admin
users to provision the MMS applications (operator admin users only) and distribution
lists (both).
• The Administration User Interface (AUI) supports the same functionality as PI.
• The CSV interface supports the provisioning of DLs and DL members.
• A command-line tool for exporting DLs is also available.
g The Mass Load Interface (MLI) does not support the provisioning of DLs.
9.1.1 DL fetch sequence

The following sequence illustrates what happens when the MMS Center performs a
profile fetch that matches a DL
1. Fetch originator profile
2. Originator is an MMS application; receiver is a DL
3. Fetch distribution list chunks

MMS NPS
Center 4. Distribution list chunks (wrapper)
5. If a resolved list, fetch the individual profile of each member
6. Receiver profiles of list members
Figure 65 Distribution list fetch by the MMS Center
98 Id:0900d80580544d7e DN70274664
Issue 5-0
1. The MMS Center does not know whether an originator of a multimedia message is
an MMS application or a subscriber, or whether the receiver is a subscriber or a DL.
Therefore, the MMS Center performs a normal originator profile fetch using an
MSISDN as the originator address, and one or several receiver MSISDN/MDNs that
may represent subscribers or DLs.
2. NPS resolves the originator profile fetch request. First it tries to fetch the originator
as a subscriber. It is not found, NPS uses the MSISDN/MDN as the MMS application
id to fetch an MMS application. If the MMS application is not found, then the resolu-
tion is continued as a normal originator profile fetch for a subscriber – the result will
be originator not found or a default originator profile. If the MMS application is found,
NPS first checks a few things:
a) Since the virtual operator (VO) profile is always resolved when an MMS applica-
tion is found, the same VO-related barring checks are done for the MMS appli-
cation as are done for a subscriber. If the VO in question has no MMS service
available, the MMS application is barred from sending MMs.
b) If the number of message receivers (it is not known yet whether they are DLs or
subscribers) exceeds the limit set by VO, the MMS application is totally barred.
c) The MMS application will be totally barred also if the MMS application is barred,
or not active in MMS service.
d) If the MMS application is not totally barred, but its validity period has ended or
not yet started, the MMS application is regarded as not found and "originator
profile not found" response is returned.
e) Now it is checked whether the customer has enabled the DL resolution from the
properties. If not, then no DL resolution is done and the originator profile of the
MMS application is resolved normally by assuming that the recipients are normal
subscribers. If the DL feature was enabled, the licence is also checked. If it is
not available, the result is the same as if the DL feature was not enabled (since
the customer may accidentally enable the DL feature).
f) If the DL resolution is to be done, then all the DL aliases of the MMS application
are fetched. If a receiver MSISDN/MDN matches to the name of a list that has
an alias with the MMS application, the receiver in question is assumed to be a
DL. If no DL of that MMS application is matched with the receiver MSISDN/MDN,
NPS assumes that the receiver is a normal subscriber MSISDN/MDN.
g) If the DL for the MMS application is found, then it is checked whether the DL is
barred. If so, then that receiver is barred from the MMS application. It is also
checked whether the alias is barred. If so, the result is the same.
h) Finally, it is checked whether the alias is expired or not yet valid. If so, the DL is
assumed not to be found and the receiver is assumed to be a normal subscriber
and the resolution continues with those assumptions.
NPS resolves the originator profile of the MMS application and checks the barrings
against the receiver information as if all the receivers were still normal subscriber
MSISDN/MDNs.
3. If the originator profile fetch response contained at least one successfully translated
DL receiver, MMS Center starts fetching the DL members from NPS in chunks with
a maximum size of 10000. If the MMS Center encounters an error (timeout, CORBA
error etc.) while fetching a chunk, it can refetch it from NPS in the same way it
fetched it for the first time. The refetch is not signaled by MMS Center to NPS in any
way. The refetching is possible also when NPS has already replied that the last
chunk was returned, since NPS does not maintain any information on the state of
fetching.
DN70274664 Id:0900d80580544d7e 99
Issue 5-0
Distribution lists Operating Guide
4. For each chunk NPS returns at most the number of DL members that MMS Center
requested. The actual number may be much smaller, even zero, depending on
possible deletions of the DL members.
g It is recommended that you do not perform DL provisioning actions when a DL
is in use. While it is possible to delete and add DL members while the MMS
Center is fetching the DL, it is not guaranteed that these provisioning actions
take effect during a DL fetch that is already in progress.
5. If the chunk indicates that the DL members are to be resolved, MMS Center will fetch
the receiver profile of each DL member with separate calls. MMS Center may fetch
the receiver profiles of several DL members for each receiver profile fetch call.
6. NPS returns the receiver profiles (or receiver not found errors, or default receiver
profiles) for each DL member as if the fetch was for receivers of a normal message
sending operation.
9.1.2 Access rights

The access right model of NPS has two important features that concern the manage-
ment of DLs:
• There is an NPS resource called the Distribution list resource. User groups that
are assigned access to this resource (read/write or read-only) can manage DLs in
the AUI and Profile Interface (PI).
• User groups can now be made MMS application specific. MMS application -specific
users are MMS application administrators, automatically limited to only accessing
the distribution list resource (read-only or read/write). If their access to the distribu-
tion list resource is read-only, they can only view the application-specific DLs.
Read/write access allows them to create, update and delete DLs that belong to their
MMS application. However, the MMS application admins cannot manage or even
view the profile of their MMS application; only the network operator (NO) and Virtual
Operator (VO) admins can do that.
There are three different kind of DLs:

• General DLs that are not VO or MMS application specific. These DLs can be
accessed by any MMS application of any VO if the administrator decides so. This
way the network operator (NO) can sell their DLs to content providers, i.e. MMS
applications.
• VO-specific DLs that are linked to particular VOs but not MMS applications. These
DLs can be accessed by the MMS applications of the VO in question if the VO admin
decides so. This way the VO can sell its DLs to content providers.
• MMS application –specific DLs that are linked to particular VOs and MMS applica-
tions. These DLs cannot be shared by other MMS applications.
Three different kind of users can create DLs if the user group has valid access rights as
such:
• NO admin users can create all three kinds of DLs. The super user also belongs to
this group.
• VO admin users can create VO and MMS application specific DLs. VO admin user
can create VO-specific DLs only to its own VO and MMS application specific DLs to
those MMS applications that it owns.
100 Id:0900d80580544d7e DN70274664

Issue 5-0
• MMS application admin users can create DLs that are linked to their own MMS appli-
cation.
9.1.3 Combining DLs with other NPS features

Using active subscriber reporting with DLs
The Subscriber Activity Reporting feature of NPS can create CSV-formatted reports of
subscriber activity. These reports can be post-processed for provisioning purposes, and
used, for example, to create a DL with the active subscribers as members.
The basic steps for provisioning a subscriber activity report as a DL are as follows:
1. Create a DL in AUI according to the instructions in section Managing distribution
lists.
2. Create a CSV format subscriber activity report file according to the desired param-
eters. For more information on how to do this, see section Subscriber activity report-
ing.
3. Process the report file so that only the MSISDN/MDNs of the subscribers remain,
each MSISDN/MDN on a separate line.
4. Use the CSV interface to provision the file as the DL content. For more information
on configuring and using the CSV interface, see the Batch Provisioning Guide.
9.1.4 Troubleshooting
If you are having problems with the DL feature, refer to the instructions in section Trou-
bleshooting distribution lists in the Troubleshooting Guide.
DN70274664 Id:0900d80580544d7e 101

Issue 5-0
Operating Guide
9.2 Managing distribution lists

Nokia Siemens Networks Profile Server (NPS) provides several ways to manage Distri-
bution Lists (DLs) and their association with MMS Applications:
• Using the Administration User Interface (AUI), NPS administrators can perform all
DL-related tasks that can be meaningfully accomplished via manual data entry.
• The Profile Interface (PI) provides the same functions as the AUI, but requires a data
provisioning client to perform the tasks. For more information, see the Profile Inter-
face Client Developer Guide.
• The CSV interface provides a way to create and manage DLs with CSV data files.
For more information, see section Overview of the CSV interface in the Batch Pro-
visioning Guide.
• There is also a command line tool that is useful for exporting the members of distri-
bution lists. For more information, see section Distribution list export tool in the Batch
Provisioning Guide.
g NPS administrators are responsible for ensuring that DLs include only valid member
addresses. From the NPS point of view, each address is only a string, and is not val-
idated. It is recommended to maintain separate lists for prepaid and postpaid sub-
scribers.
9.2.1 Creating distribution lists
1. Log in to AUI as a user with access to the Distribution lists resource. If you log in
as an operator-specific user, you can only manage the distribution lists (DLs) of your
own operator, and the sub-operators it may have.
2. Click Distribution lists in the vertical menu. The Distribution lists page opens.
3. On the distribution lists page, you can search for existing lists, create new lists, and
delete lists. You can use wildcards "*" (asterisk) and "?" (question mark) in your
searches. To create a new distribution list, click the New button. The New
distribution list page opens.
102 Id:0900d80580525d47 DN70274664

Issue 5-0
Operating Guide
Figure 66 AUI - Distribution lists page with search results

4. Specify the properties of the new distribution list according to the following fields on
the New distribution list page:
• Operator: This selection allows you to make the list operator-specific, or allow
it for all operators. If you are logged in as an operator-specific user, you can only
create operator-specific lists.
• MMS application: You can make the list specific to one application only. If
selected, the list cannot be used by other applications.
• List name: The name of the distribution list, used as the unique identifier for the
list. Note: the name of the list cannot be changed after the list has been
created.
• Description: Description of the list.
• Barred: If this checkbox is set, the distribution list is entirely barred and will not
be found when the MMS receiver is being resolved.
• Resolved: If this checkbox is set, the personalised push feature is enabled, and
the profiles of all list members are individually resolved. Note that it is possible
set this checkbox even if the personalised pushfeature is not enabled by the
current NPS licence. If the licence is not OK, the feature will not work even if
selected.
• IMSI query: If this checkbox is set, the MMS Center will perform an IMSI query
for each list member.
DN70274664 Id:0900d80580525d47 103

Issue 5-0
Operating Guide
• Delay time ___ minutes: The number of minutes the MMS Center will wait after
fetching a set number of list members (specified in the next field). If specified,
also the following field must be specified.
• Delay after fetching ___ 0000 list members: The number of list members after
which the MMS Center will wait a set number of minutes (specified in the
previous field). If specified, also the previous field must be specified. The
number is always multiple of 10,000 (ten thousand), so if you enter the value 2,
the MMS Center will delay after processing 20000 list members.
If you provision this value using the data provisioning interfaces, always use
non-negative multiples of 10,000 as the value.
• Content adaptation: Specifies whether content adaptation is allowed for the list
members. Possible values are Allowed, Not allowed and Unknown.
• Prepaid: If this checkbox is set, all list members are indicated to be prepaid.
Figure 67 AUI - New distribution list

5. After configuring the list settings, click the Update button to create the list. Now that
the list is created, you can proceed to set up the MMS application aliases that you
need, and provision the list members.
104 Id:0900d80580525d47 DN70274664

Issue 5-0
Operating Guide
9.2.2 Managing existing lists

1. Log in to AUI as a user with access to the Distribution lists resource. If you log in
as an operator-specific user, you can only manage the distribution lists (DLs) of your
own operator, and the sub-operators it may have.
2. Click Distribution lists in the vertical menu. The Distribution lists page opens.
3. On the distribution lists page, you can search for existing lists, create new lists, and
delete lists. You can use wildcards "*" (asterisk) and "?" (question mark) in your
searches.
To delete a distribution list, select the corresponding checkbox in the search result
list, and click Delete. Clicking the name of a list opens the Distribution list details
page, which also has a delete button.
To modify a list, click the name of a list in the search results. The General tab under
the Distribution list details page opens.
4. The top of the General tab displays the following information:
• Is the list operator-specific
• Is the list dedicated to a single MMS application
• The size of the list (number of list members)
Additionally, the General tab displays the following editable fields:
• List name: The name of the distribution list, used as the unique identifier for the
list. Cannot be changed after the list has been created.
• Description: Description of the list.
• Barred: If this checkbox is set, the distribution list is entirely barred and will not
be found when the MMS receiver is being resolved.
• Resolved: If this checkbox is set, the personalised push feature is enabled, and
the profiles of all list members are individually resolved.
• IMSI query: If this checkbox is set, the MMS Center will perform an IMSI query
for each list member.
• Delay time ___ minutes: The number of minutes the MMS Center will wait after
fetching a set number of list members (specified in the next field).
• Delay after fetching ___ 0000 list members: The number of list members after
which the MMS Center will wait a set number of minutes (specified in the
previous field). The number is always multiple of 10,000 (ten thousand), so if you
enter the value 2, the MMS Center will delay after processing 20000 list
members.
If you provision this value using the data provisioning interfaces, always use
non-negative multiples of 10,000 as the value.
• Content adaptation: Specifies whether content adaptation is allowed for the list
members. Possible values are Allowed, Not allowed and Unknown.
• Prepaid: If this checkbox is set, all list members are indicated to be prepaid.
5. The List Members tab displays a search page where you can perform wildcard
searches among the members of the current distribution list.
To add new members, click the New button. The New distribution list members
page opens, where you can use the Add button to create more address fields. Click
the Create button when done.
To delete list members, check their Delete checkbox in the search result list, and
click the Delete button.
DN70274664 Id:0900d80580525d47 105

Issue 5-0
Operating Guide
Figure 68 AUI - Distribution list members

6. The MMS application aliases tab displays a search page where you can perform
wildcard searches among the MMS application aliases of the current distribution list.
To delete existing MMS application aliases, check their Delete checkbox in the
search result list, and click the Delete button.
To modify an existing MMS application alias, click its name in the search result list.
You can modify all of the fields that are available when creating a new MMS appli-
cation alias; see the next step.
106 Id:0900d80580525d47 DN70274664

Issue 5-0
Operating Guide
Figure 69 AUI - MMS application aliases

7. To create new MMS application aliases, click the New button. The New MMS
application alias page opens.
Define the MMS application alias using the following fields:
• MMS application: Use the drop-down menu to select the MMS application to be
associated with this alias.
• Alias: Enter the alias to be used.
• Barred from this MMS application: If this checkbox is set, the distribution list
is barred and not available from the selected MMS application. Does not affect
other MMS applications or the access to other distribution lists.
• Validity start date: The distribution list can be used by the specified application
beginning from the date set here. If no date is set, the list is immediately avail-
able. The format is YYYY.MM.DD hh:mm:ss.
• Validity end date: The distribution list can be used by the specified application
until the date set here. If no date is set, the list will always be available (unless
prevented by barring, etc.). The format is YYYY.MM.DD hh:mm:ss.
DN70274664 Id:0900d80580525d47 107

Issue 5-0
Operating Guide
Figure 70 AUI - New MMS application alias

After defining the MMS application alias, click Create.
108 Id:0900d80580525d47 DN70274664

Issue 5-0
Operating Guide Managing NTMS groups
10 Managing NTMS groups

Purpose
NTMS can assign subscribers into NTMS groups. Before a subscriber can be associ-
ated with a group, this group must exist in the Profile Server. Follow the procedure below
to manage NTMS groups.
g The NTMS groups do not affect the profile resolution process; they are for the
benefit of NTMS only.
Steps
1 Log in to AUI as non operator-specific user with access to the NTMS groups
resource.
2 Click NTMS groups in the vertical menu bar.

The NTMS groups page opens with a list of currently existing NTMS group names.
Figure 71 AUI - NTMS groups
3 To create a new NTMS group, click New.

The New NTMS group page opens.
DN70274664 Id:0900d80580544da5 109

Issue 5-0
Managing NTMS groups Operating Guide
Figure 72 AUI - New NTMS group page
4 Enter a name and description for the new group, and click Create.
g All NTMS group names must begin with NTMS_. For example: NTMS_group.
5 To delete an NTMS group, check its checkbox on the NTMS groups page and click
the Delete button.
You can only delete an NTMS group if there are no subscribers associated with it.
110 Id:0900d80580544da5 DN70274664

Issue 5-0
Operating Guide Managing terminal models
11 Managing terminal models

Nokia Siemens Networks Profile Server (NPS) maintains a list of terminal models and
their capabilities in the NPS database. The terminal model ID (for example, Nokia
6600) serves as the link to the terminal's capability information. The terminal model def-
initions are used when the Nokia Siemens Networks Terminal Management Server
(NTMS) creates a link between a subscriber (based on MSISDN/MDN) and a particular
IMEI code. NTMS also associates the subscriber with a particular terminal model, and
NPS uses the MMS capability information of the terminal model to adjust the Terminal
capability in the MMS service profile of the subscriber.
g The terminal capability of the subscriber's MMS profile is only adjusted when NTMS
associates the subscriber with a terminal model. It is not done if you change the sub-
scriber's terminal model in the AUI. Also, if you change the MMS capability of the
terminal model, the change is not applied automatically to all existing subscribers
with that terminal model.
NTMS can provision the terminal models directly to the NPS database. However, the
terminal models can also be managed using the Administration User Interface (AUI).
For more information on the NTMS support of the NPS, see section Overview of NTMS
support in the Integration Guide.
11.1 Managing terminal models using the AUI

1. Log in to AUI as a user with access to the NTMS groups & Terminal models
resource. The resource is only available to user groups that are not operator-spe-
cific.
2. Click Terminal models in the vertical menu. The Terminal models page opens.
On the terminal models page, you can search for existing terminal models, create
new models, and delete models. You can use wildcards "*" (asterisk) and "?" (ques-
tion mark) in your searches.
DN70274664 Id:0900d80580525dca 111

Issue 5-0
Managing terminal models Operating Guide
Figure 73 AUI - Terminal models

3. To delete a terminal model, set the corresponding checkbox in the search results list
and click the Delete button.
4. To create a new terminal model, click the New button. The New terminal model
page opens.
Enter the Terminal model ID, and select the MMS capability setting from the drop-
down list. Possible values are Unknown, MMS capable and Not MMS capable.
When done, click the Create button.
112 Id:0900d80580525dca DN70274664

Issue 5-0
Operating Guide Managing terminal models
Figure 74 AUI - New terminal model

5. To open a terminal model for editing, click the name of the model in the search
results list to enter the Terminal model details page. If you have just created a new
terminal model, you are already on that page.
The Terminal model ID cannot be changed after the terminal model has been
created, but you can change the MMS capability setting. Additionally, you can add
parameter-value pairs as Static terminal settings for this terminal model. Click the
Add button to add new fields, and Delete to delete existing fields.
When done, click the Update button.
Figure 75 AUI - Terminal model details
DN70274664 Id:0900d80580525dca 113

Issue 5-0
Overview of SMSC configurations Operating Guide
12 Overview of SMSC configurations

NPS can store the configurations for Subscriber User Group (SUG) functionality of the
SMSC. This allows you to customise the SMSC behaviour per subscriber. On the SMSC
Configurations pages in the AUI, configurations can be created for different SUG fea-
tures. After a configuration has been created, it can be assigned to a subscriber by
updating the SMSC preferences of the subscriber. For more information, see section
Subscriber - SMSC Preferences
The following SUG features are supported:
• Delivery Attributes
• Content Based Filtering
• Incoming Capacity Allocation
• Regional Barring
• Lawful Trace
In addition to these SUG features, there is also support for additional configurations, if
needed by the SMSC. Each of the features also has support for additional configuration
parameters. For detailed information about each configuration parameter, refer to the
SMSC SUG documentation.
In addition to the parameters detailed in the SMSC SUG documentation, each configu-
ration has a mandatory id and an optional name. The id is used when linking subscribers
to the SUG configurations, and the name can be free form text by which it is easier to
remember what the purpose of the group is.
12.1 Creating new SMSC configurations

1. Log in to AUI as a user with access to the SMSC configuration resource.
2. Click SMSC configuration in the vertical menu. The SMSC configuration -
Delivery Attributes page opens.
3. Click on the link on the horizontal menu at the top of the page which corresponds to
the feature to be configured.
4. When on the correct page, click the New button.
NPS will automatically suggest the next free id value for the configuration.
114 Id:0900d80580544e1a DN70274664

Issue 5-0
Operating Guide Overview of SMSC configurations
5. Fill in the configuration parameters.
6. To create the configuration, click the Create button.

7. If you need to cancel the creation process, click the Cancel button.
12.2 Updating existing SMSC configurations

1. Log in to AUI as a user with access to the SMSC configuration resource.
2. Click SMSC configuration in the vertical menu. The SMSC configuration - Delivery
Attributes page opens.
3. Click on the link on the horizontal menu at the top of the page which corresponds to
the feature to be edited or updated.
DN70274664 Id:0900d80580544e1a 115

Issue 5-0
Overview of SMSC configurations Operating Guide
4. When on the correct page, choose the configuration to be updated by clicking the
link in the Id column.
5. After you have updated the configuration, click Update to save the configuration.
6. If you need to discard the changes, press Cancel.
116 Id:0900d80580544e1a DN70274664

Issue 5-0
Operating Guide Managing additional parameters
13 Managing additional parameters

In Nokia Siemens Networks Profile Server (NPS) you can store operator-defined param-
eters in the profiles of the operator, subscriber type, and subscriber entities. The addi-
tional parameters are a part of the profile resolution process: the operator can define
new parameters on the subscriber type and operator level, and the new parameters will
automatically be included when the profiles are fetched. The operator-level and sub-
scriber type -level parameters will be included in the profiles unless the subscriber's
profile contains a different value for the parameter.
This full implementation of the additional parameters allows the operators to more con-
veniently use the NPS as a database for parameters that do not exist by default. For
example, network elements which have not been pre-integrated with NPS can now be
supported using Profile Interface clients.
The operators can provision additional parameters for the subscribers through the
Administration User Interface (AUI) and all of the data provisioning interfaces. The pro-
visioning of the additional parameters for the operator and subscriber type entities is
possible via the Profile Interface and the AUI.
The operator can develop a client application to fetch the new parameters through the
SOAP Interface. Retrieving the additional parameters for subscribers is also supported
through the Generic Profile Fetch API (GPFAPI).
g Additional parameters are a licensable feature; you must purchase a licence to be
able to store and fetch the additional parameters. If the licence does not enable addi-
tional parameters, the corresponding pages in the AUI will not function.
If you do not have the necessary licence, you can hide the pages from the AUI. For
instructions, see section Configuring AUI in the Administration Guide.
13.1 Managing additional parameters using the AUI

The Administration User Interface (AUI) has dedicated pages for managing the addi-
tional parameters that have been defined on the subscriber, subscriber type, and
operator level. These pages are accessed by clicking the Additional parameters link
in the vertical menu.
To access the pages, the user's user group must have access to the corresponding
resource. For more information on access rights, see section Overview of user manage-
ment.
g The attributes that have been defined as default attributes on the operator, sub-
scriber type, or subscriber level cannot be defined as additional parameters. For
instance, you cannot add gender as an additional parameter because it has already
been defined on the Subscriber - personal information page. Defining two differ-
ent values for the same attribute raises an alarm in the Advertising Application.
13.1.1 Additional parameters - subscriber

This page requires access to the Subscribers & Additional parameters resource.
To manage the additional parameters that have been defined for a subscriber, you must
first locate the subscriber by searching. The search functions exactly as the search on
the Subscribers page. For more information, see section Modifying a subscriber.
DN70274664 Id:0900d80580525eff 117

Issue 5-0
Managing additional parameters Operating Guide
Figure 76 AUI - Additional parameters - subscriber search

To manage the additional parameters in a subscriber's profile, click the name of the sub-
scriber in the search result list. A page with the currently defined parameters opens.
Figure 77 AUI - Additional parameters - subscriber's additional pameters

To edit the value of a parameter, enter a new value in the value field. If you enter a new
value for a parameter that has been resolved from the operator or subscriber type level
(indicated by the greying out of the parameter name), the parameter will be created in
the subscriber's profile with the new value.
Use the Add button to create new fields for entering parameter names and values. To
delete an existing parameter-value pair, click the corresponding Delete button.
When you have done editing, click the Update button to commit your changes, or the
Cancel button to discard them.
118 Id:0900d80580525eff DN70274664

Issue 5-0
Operating Guide Managing additional parameters
13.1.2 Additional parameters - subscriber type

This page requires access to the Subscriber types & Additional parameters
resource.
To manage the additional parameters that have been defined for a subscriber type, you
must first select the subscriber type from the list on this page. If your user account is not
operator-specific, you must first select an operator to view the listing of subscriber types
for that operator.
Figure 78 AUI - Additional parameters - subscriber type list

The parameter-value pairs are managed in the same way as on the subscriber's
Additional parameters page.
13.1.3 Additional parameters - operator

This page requires access to the Operators & Additional parameters resource, and a
user account that is not operator-specific.
To manage the additional parameters that have been defined for an operator, simply
select the operator's name from the drop-down list on this page.
The parameter-value pairs are managed in the same way as on the subscriber's
Additional parameters page.
DN70274664 Id:0900d80580525eff 119

Issue 5-0
Subscriber activity management Operating Guide
14 Subscriber activity management
14.1 Creating subscriber activity reports

Purpose
Using the Subscriber Activity Management feature, you can create reports of subscriber
activity using the AUI. The reports are created based on the number of times that the
service profile of a subscriber is fetched by the corresponding network element.
You can create the following kinds of reports:
• Activity summary reports display a breakdown of subscribers that have the
desired activity level for each operator and interface.
• Detailed activity reports include the MSISDN/MDN of each subscriber that
matches the activity criteria. For the report type MMS MO-MT, also the MMS
receiver is included, as well as the operator of both subscribers.
• Detailed inactivity reports include the MSISDN/MDN of each subscriber that
matches the inactivity criteria. These reports can be very large, since it is easy to
enter criteria that will match every subscriber in the database.
The reports are saved as CSV files, and can be post-processed for provisioning pur-
poses.
The subscriber activity management feature can only be used if you have installed a
licence file that enables it.
g Due to the way the Nokia Siemens Networks Application Gateway (AGW) uses
NPS, it is not included in subscriber activity management. The events generated by
the AGW GUI cannot be distinguished from actual subscriber activity.
The report files are created from logging data that is stored in the NPS database. To
learn more about the logging capabilities of the NPS, and the available configuration
possibilities, see section Configuring logging in the Administration Guide.
Steps
1 Log in AUI as a user with access to the Active subscriber Mgt resource.
2 Click Subscriber activity in the vertical menu bar.

The Subscriber activity files page opens:
120 Id:0900d80580547f7e DN70274664

Issue 5-0
Operating Guide Subscriber activity management
Figure 79 AUI - Subscriber activity files

The list on the page shows the previously generated subscriber activity reports. To view
a report or save it as a CSV file, click the name of the file in the list. To delete a report,
check the Delete checkbox next to the name of the report, and click the Delete button
at the bottom of the page.
If the report file is very large, it may take considerable time to download and display the
file. For large report files, it is recommended that you transfer the files via FTP, and do
not view them by clicking the file name. The report files are kept in directory
/var/opt/profiler6/activityfiles.
3 To create a new subscriber activity summary report, click the New button.
The New subscriber activity summary report page opens:
DN70274664 Id:0900d80580547f7e 121

Issue 5-0
Figure 80 AUI - New subscriber activity summary report

Set the following options to create the subscriber activity summary report:
• Operator: Select <<for each>> to produce a report for all operators, or select an
operator to limit the report to the data for that particular operator. You can only select
the operators that your user account has access to.
• Output: Use the radio button to select whether you want the report to be stored in a
CSV file, or displayed on the screen.
• Activity type: Select the activity type to be included in the report, or select <<for
each>> to create a report including all types. The activity types correspond to the
subscriber service profiles:
• CA
Profile fetch events by the Nokia Siemens Networks Content Analyzer.
• DLS
Profile fetch events by the Nokia Siemens Networks Delivery Server.
• GGSN
Profile fetch events by the Nokia Siemens Networks Gateway GPRS Support
Node.
122 Id:0900d80580547f7e DN70274664

Issue 5-0
• MMS MO
MMS originator profile fetch events by the Nokia Siemens Networks MMS
Center.
• MMS MO-MT
Profile fetch events by the Nokia Siemens Networks MMS Center for each MMS
originator-receiver pair.
• MMS MT
MMS receiver profile fetch events by the Nokia Siemens Networks MMS Center.
• PRS
Profile fetch events by the Nokia Presence Server.
• TA
Profile fetch events by the Nokia Siemens Networks Terminal Analyzer.
• VOIP
Profile fetch events by the Nokia Siemens Networks VoIP Server.
• Activity reporting threshold: Minimum number of events during the reporting
period after which a subscriber is included in the report. If <<for each>> is selected
as the client type, the limit applies independently to each client type.
• Begin time and End time: Set the beginning and end for the reporting period. The
format is dd.MM.yyyy HH:mm, for example 17.11.2005 00:00.
When done, click the Create button to generate the report. When it is ready, the report
will be displayed on screen, or it will appear in the list of subscriber activity reports in the
CSV format, depending on your output choice.
4 To create a detailed subscriber activity report, click the New button, and then the
Active detailed tab.
The New subscriber activity report page opens:
DN70274664 Id:0900d80580547f7e 123

Issue 5-0
Figure 81 AUI - New subscriber activity report

Using the reporting criteria on this page, you can create detailed subscriber activity
reports with content such as:
• Subscribers that sent at least 5 MMS messages during the last Saturday.
• Subscribers of operator X that sent at least 10 MMS messages last week.
• Subscribers that sent at least one MMS message between 10:00 pm and 11:00 pm
last night.
Set the following options to create the detailed subscriber activity report. Note that you
cannot select the output; detailed activity reports are always created as CSV files.
• Activity type: Select the type of activity to be reported. The activity types corre-
spond to the subscriber service profiles:
• CA
• DLS
124 Id:0900d80580547f7e DN70274664

Issue 5-0
• GGSN
Node.
• MMS MO
Center.
• MMS MO-MT
Profile fetch events by the Nokia Siemens Networks MMS Center for each MMS
originator-receiver pair.
• MMS MT
• PRS
• TA
• VOIP
• Activity reporting threshold: Minimum number of events during the reporting
period after which a subscriber is included in the report.
When done, click the Create button to generate the report. When the report is ready, it
will appear in the list of subscriber activity report files.
5 To create a detailed subscriber inactivity report, click the New button, and then
the Inactive detailed tab.
Be careful when creating detailed subscriber inactivity reports. You can easily produce
huge report files that include every subscriber in the database. Huge report files can
cause problems by filling up the /var filesystem. The report files are kept in directory
/var/opt/profiler6/activityfiles.
The New subscriber inactivity report page opens:
DN70274664 Id:0900d80580547f7e 125

Issue 5-0
Figure 82 AUI - New subscriber inactivity report

Using the reporting criteria on this page, you can create detailed subscriber inactivity
reports with content such as:
• Subscribers that sent less than two MMS messages last month.
• Subscribers that have received less than two MMS messages last week.
Set the following options to create the detailed subscriber inactivity report. Note that you
cannot select the output; detailed inactivity reports are always created as CSV files.
• Activity type: Select the type of activity to be reported. The activity types corre-
spond to the subscriber service profiles:
• CA
• DLS
• GGSN
Node.
126 Id:0900d80580547f7e DN70274664

Issue 5-0
• MMS MO
Center.
• MMS MT
• PRS
• TA
• VOIP
• Activity reporting threshold: Maximum number of events during the reporting
period under which a subscriber is included in the report. In the inactivity reports,
subscribers whose activity equals the threshold value are not included in the report.
When done, click the Create button to generate the report. When the report is ready, it
will appear in the list of subscriber activity report files.
Further information
The format of the different subscriber activity report types are described in section Sub-
scriber activity report formats.
DN70274664 Id:0900d80580547f7e 127

Issue 5-0
Operating Guide
14.2 Subscriber activity report formats

This section presents the CSV structure of the subscriber activity report files. For instruc-
tions on how to create subscriber activity reports, see section Creating subscriber
activity reports.
14.2.1 Activity summary report format

The format of an activity summary report is as follows:
• The first line contains the activity limit, begin time, and end time that
were specified when the report was generated.
• The second line contains the word operator and the activity types that are
included in the report.
• Each line after the second one contains the data for one operator.
Example report, showing GGSN and MMS activity for operator operator.com, and CA
and TA activity for subvo:
activity limit=5,begin time=20060208000000,end time=20060215000000
operator,CA,DLS,GGSN,MMS,PRS,TA,VOIP
operator.com,0,1833,0,233004,0,0,0
subvo,23435,0,0,0,0,562221,0
14.2.2 Detailed activity report format

The format of a detailed activity report is as follows:
• The first row contains the activity limit, begin time, end time, and
activity type that were specified when the report was generated.
• The second row is the header row for fields included in the subsequent data. For
most of the report types, the second line only contains the word MSISDN. Since the
data for the report type MMS MO-MT contains MMS originator-receiver pairs, the
format is more complex, and includes the operator VOId of the subscriber's opera-
tors: operator,MSISDN,receiver,operator.
• The rest of the rows in the report file are data rows, with the structure that is specified
on the second row.
Example report for activity type CA of a given operator:
activity limit=5,begin time=20060208000000,end time=20060215000000,activity type=CA
MSISDN
01012345
01023456
05023456
05087654
...
Example report for activity type MMS MO-MT:

activity limit=5,begin time=20060208000000,end time=20060215000000,activity type=MMS MO-MT
operator,MSISDN,RECEIVER,operator
operator.com,01045634,2320945,sub-vo
subvo,23423234,2222345,operator.com
exampleoperator,89067066,0678966,operator.com
operator.com,34836736,4784322,sub-vo
...
128 Id:0900d80580525f78 DN70274664

Issue 5-0
Operating Guide
14.2.3 Detailed inactivity report format

The format of a detailed inactivity report is as follows:
• The first row contains the inactivity limit, begin time, end time, and
inactivity type that were specified when the report was generated.
• The second row is the header row for fields included in the subsequent data. For the
inactivity reports, the second row only contains the word MSISDN.
• The rest of the rows in the report file are data rows, containing the MSISDN/MDNs
of the subscribers included in the report.
Example report for inactivity type MMS MO of a given operator:
inactivity limit=4,begin time=20060306000000,end time=20060313000000,inactivity type=MMS MO
MSISDN
01012345
01023456
05023456
05087654
...
g Generating operator specific reports decreases the size of the file, since the VOId
is not included in the report.
DN70274664 Id:0900d80580525f78 129

Issue 5-0
Reporting Operating Guide
15 Reporting
15.1 Viewing current traffic

Purpose
In the AUI, you can view the current profile fetch traffic in the system.
Steps
1 Log in AUI as a user with access to the Current traffic & Counters resource.
If you log in with an operator-specific account, you will only be able to view the current
traffic for your own operator, and the subordinate operators (sub-VOs) that have been
created for it.
2 Click Current traffic in the vertical menu bar.
3 Select <<all>> to view the profile fetch traffic for all operators, or choose an
operator to view.
The <<for each>> selection is only available if you have access to the traffic information
for more than one operator. For operator-specific users, the <<for each>> selection will
display the traffic of their own operator, and the sub-VOs that it controls.
Click Search after selecting.
4 The current traffic page will be displayed.

The page will display the combined profile fetch traffic for all profile fetch interfaces for
the last 10 minutes. The traffic for each minute is displayed on a separate row.
Figure 83 Current traffic
130 Id:0900d80580547f91 DN70274664

Issue 5-0
Operating Guide
15.2 Creating counter report files

Purpose
In the AUI, you can generate reports using the counters stored by the logging system or
query subscriber counters from the database. You can generate reports for all opera-
tors, or for a single operator only. You can save the reports as CSV files, and view some
reports on the screen. You can also preset subscriber reports to be run recurringly.
Steps
1 Log in to the AUI as a user with access to the Current traffic & Counters resource.
2 To view reports
Steps
a To view counter report files, click Counters in the vertical menu bar.
The default view is of the Counter report files page, with a list of the currently created
reports.
Figure 84 AUI - Counter reports default view
DN70274664 Id:0900d80580547fa3 131

Issue 5-0
Operating Guide
b To view scheduled report files, click the Scheduled reports tab.
Figure 85 AUI - Scheduled reports default view
3 Create and view a new traffic report
Steps
a In the default view, click New.
b Make sure the Traffic report tab is selected.
c Set the report parameters from the drop-down menu.

• Report: The report type.
• Subscriber 1: Number of subscribers.
• Subsciber 2: Number of subscribers per subscriber type.
• Traffic 1: Number of successful profile fetches per client type.
• Traffic 2: Number of autoprovisioning events per client type.
• Traffic 3: Number of provisioning events.
• Traffic 4 - Number of successful notifications.
• Traffic 5 - Number of intercepted subscriber events.
• Traffic 6 - Number of failed profile fetches per client type.
• Traffic 7 - Number of failed notifications.
• Traffic 8 - Number of SOAP requests. This report type does not consider the
operator.
• Traffic 9 - Number of LDAP requests.
• DL 1 - Number of DL members fetched per MMS application.
• DL 2 - Number of DL fetches per MMS application.
• DL 3 - Number of DL members fetched per DL.
• DL 4 - Number of DL fetches per DL.
• SAIF 1 - Maximum number of concurrent SAIF users.
• SAIF 2 - Number of unauthorized SAIF login attempts. This report type does
not consider the operator.
132 Id:0900d80580547fa3 DN70274664

Issue 5-0
Operating Guide
d Select the operator from the drop-down menu.

Operator: Select <<for each>> to produce a report for all operators, or select an
operator to limit the report to the data for that particular operator. The <<all>> option
is displayed only if more than one operator is defined in the system, and the current
user is not operator-specific.
e Select the required form of output.

Output: Select CSV file to save the report as a file, or Screen to view the report on-
screen.
f Set the reporting period by filling in the required beginning and end times.
Reporting period in Traffic and SAIF reports: The beginning and end of the
reporting period. The format is dd.MM.yyyy HH:mm, for example 17.03.2004
00:00.
When entering the beginning and end times, you must enter the minutes so that they
are divisible by the reporting Interval, beginning from 00. For example: for 15 minute
reporting interval, you can enter the minutes 00, 15, 30 or 45. If the times are entered
incorrectly, you will receive an error when you click the Create button.
g Set the required interval from the drop-down menu.

Interval: The interval at which the traffic and SAIF reports will display the data. You
may also set the interval to be the entire reporting period.
h Click Create to generate the report.
i To view traffic reports, click on Counters in the vertical menu bar.

Clicking the name of a report in the Counter report files view will give you the option
to view or save it. To delete a report, check the Delete checkbox next to the name
of the report, and click on the Delete button at the bottom of the page.
4 Create and view a new subscriber report
Steps
b Make sure the Subscriber report tab is selected.
Figure 86 AUI- Creating new subscriber report
DN70274664 Id:0900d80580547fa3 133

Issue 5-0
Operating Guide
c Set the report parameters from the drop-down menu.

• Subscriber 1: Number of subscribers.
• Subsciber 2: Number of subscribers per subscriber type.
e Select the required form of output (CSV file or screen).
f Click Create to generate the report.
g To view Subscriber reports, click on Counters in the vertical menu bar.

Clicking the name of a report in the Counter report files view will give you the option
to view or save it. To delete a report, check the Delete checkbox next to the name
of the report, and click on the Delete button at the bottom of the page.
5 Create and view a new Scheduled subscriber report.
Figure 87 AUI- Scheduled subscriber report default view
Steps
b Make sure the Scheduled subscriber report tab is selected.
134 Id:0900d80580547fa3 DN70274664

Issue 5-0
Operating Guide
c Fill in the File/task ID* field.
e Check the Group box if necessary.
f Select a group type and set the corresponding definition from the drop-down
menus.
Group types
• Subscriber type
• Prepaid type
• Postpaid
• Prepaid
• Corporation
• Terminal model
g Check the Parameter box if necessary, and fill in the required fields.
(See default view)
h Set recurrence.
Select one of the following:
• Monthly
• Weekly
• Daily
• Only once
i Click Create to view the report in the default view.
DN70274664 Id:0900d80580547fa3 135

Issue 5-0
Operating Guide
j In the default view, click on the report.
Figure 88 Created report default view

Here you can set the activity of the report, create it immediately, or cancel the report.
• To generate a report, click Create.
• Clicking the name of a report in the Counter report files view will give you the
option to view or save it. To delete a report, check the Delete checkbox next to
the name of the report, and click on the Delete button at the bottom of the page.
136 Id:0900d80580547fa3 DN70274664

Issue 5-0
Operating Guide
15.3 Creating transaction log files

Purpose
In the AUI, you can generate transaction log files of four pre-determined types. You can,
for example, create a log file of all autoprovisioned subscribers within the last week.
The log files are created from transaction log data that is stored in the NPS database.
To learn more about the logging capabilities of the NPS, and the available configuration
possibilities, see section Configuring logging in the Administration Guide.
Steps
1 Log in AUI as a user with access to the transaction logs resource.
2 Click Transaction logs in the vertical menu bar.

The Transaction log files page opens:
Figure 89 AUI - Transaction log files

To view a transaction log or save it as a CSV file, click the name of the log file in the list.
To delete a log file, check the Delete checkbox next to the name of the log, and click the
Delete button at the bottom of the page.
3 To create a new log file, click the New button.

The New log file page opens:
DN70274664 Id:0900d80580547fac 137

Issue 5-0
Operating Guide
Figure 90 AUI - New log file page
• Log: Select the log type:

• Autoprovisioned subscriber log creates a log file of all autoprovisioning
events.
• AUI action log creates a log file of AUI provisioning actions.
• Deleted subscriber log creates a log file of all subscriber deletions.
• Intercepted subscriber event log creates a log file which displays all recorded
events for subscribers that have been flagged for interception.
• Intercepted DL fetch log creates a log file which displays all recorded distribu-
tion list (DL) fetch events involving MMS applications that have been flagged for
interception.
• Intercepted DL provision log creates a log file which displays all recorded dis-
tribution list (DL) provisioning events involving MMS applications that have been
flagged for interception.
operator to limit the report to the data for that particular operator. Operator-specific
users cannot select the <<for each>> option.
4 Click the Create button to generate the log file.

When the file is ready, it will be visible in the list on the Transaction log files page.
138 Id:0900d80580547fac DN70274664

Issue 5-0
Operating Guide
15.4 Viewing audit trail

Purpose
The Audit trail feature provides means to monitor changes made to NPS system through
AUI. It is also possible to monitor actions like logins, logouts and changes of NPS
profiles made by NPS clients. Through Audit trail it is possible to answer questions: what
has been made, who has done it, through which client type and when. The Audit trail
feature applies to PI based interface usage only. This means the following interfaces:
AUI, AG, CA, DLS, GGSN, MMS, PROV, PRS, SMSC, TA and VOIP. In practice the
Audit trail means that PI requests are logged individually to the database. The logs can
be browsed through AUI. You can configure which components write audit trail logs and
which methods are logged.
g Changes made through command line interface, CSV, MLI and legacy DP are not
included in Audit trail.
Steps
1 To use the audit trail feature, log into AUI as a user with access to the Audit trail
resource.
2 To reach the Audit trail view, Click Audit trail in the menu list on the left.
Audit trail is located under Reports. The following view appears:
Figure 91 AUI Audit trail view
3 Enter the times between which you wish to view the audit trail from in the Begin
time and End timefields.
4 Select a user from the drop-down menu.
5 Click the interface type you wish to use.
DN70274664 Id:0900d80580547faf 139

Issue 5-0
Operating Guide
6 Select a method from the drop-down menu.
7 Click your preferred response status.
8 Click SEARCH.
140 Id:0900d80580547faf DN70274664

Issue 5-0
Operating Guide System management
16 System management
16.1 Managing components

Clicking Components in the vertical menu of the Administration User Interface (AUI)
opens the Components page which lists the currently enabled components and their
status. The components link can only be made accessible for non operator-specific
administrator users.
Figure 92 AUI - Components page (partial)

For a reference on the purpose of each component, including the components not visible
in the AUI, see section NPS components in the Administration Guide.
Each component is displayed on its own row. The row contains the name of the compo-
nent, the host on which the component is running, its status, and a button for starting,
stopping or restarting the component. These buttons should be used when it is neces-
sary to start or stop a component. It is also possible to start and stop components from
the command line, by using the Component Control (CCTL) tool. For more information,
see section Managing Components using the CCTL in the Troubleshooting Guide doc-
ument.
It is important to remember that only the components which are enabled in the configu-
ration files of their managers are displayed on this page. Component which are disabled
cannot be enabled on this page; you have to do manual configuration actions to enable
them. For instructions on how to do this, see section Enabling and disabling components
in the Administration Guide document.
The name of the component serves as a link to the Component details page of the
component. The details page displays information relevant to the component, if any. The
details page of the LICAUTH_1 component, for example, shows the features and
capacity enabled by the currently used license file:
DN70274664 Id:0900d80580547fb7 141

Issue 5-0
System management Operating Guide
Figure 93 Component details page for LICAUTH_1 component

For example, The details page for the MMSCCORE_1 component provides convenient
statistics on the MMS profile fetch activity:
142 Id:0900d80580547fb7 DN70274664

Issue 5-0
Operating Guide System management
Figure 94 Component details page for MMSCCORE_1 component (partial)
DN70274664 Id:0900d80580547fb7 143

Issue 5-0
Operating Guide
16.2 Managing component groups

Clicking Component Groups in the vertical menu of the Administration User Interface
(AUI) opens the Component Groups page which lists the status of the component
groups currently configured in the system.
Figure 95 AUI - Component Groups page of NPS running on single machine (partial)
Each group is displayed on its own row. In an NPS system running on a single machine,
each row consists of the name of the group and the status of the group. The group status
is a link to detailed information about the group. In an NPS system running on a cluster,
each row consists of the name of the group, the cluster wide status of the group, and the
status of the group on each node of the cluster. The group status on each node is also
a link to more detailed information for the group on that particular node.
The Component group details page shows the current status of the group, and it shows
the components that are configured for the group. If a group is active, the status of the
components belonging to the group can be seen in the Components page on the AUI.
On the Component group details page, it is also possible to stop and start the compo-
nent group in question. The AUI group is an exception, because it can only be stopped
from the command line interface.
144 Id:0900d80580547fcf DN70274664

Issue 5-0
Operating Guide
16.3 Editing configuration files

Purpose
Many of the configuration tasks for Nokia Siemens Networks Profile Server (NPS)
require manual editing of configuration files. This procedure contains instructions for
editing configuration files through the Administration User Interface (AUI). It is naturally
also possible to edit the files from the command line; sometimes it is even necessary.
For more information on manual editing, see Further information at the end of the pro-
cedure.
There are some configuration files that cannot be edited from the AUI. When these files
must be edited, specific instructions are given with regard to the location and required
access rights.
NPS performs validation on most of the values in the configuration files. This is done to
guarantee that mandatory values are present, and that the values are of the valid type.
If the validation detects an invalid configuration, the alarm 28821 CONFIGURATION
INVALID will be raised, and the issues logged into the trace log. System defaults will be
used instead of the invalid values.
The alarms are sent periodically and the errors are logged to the trace log as long as the
problems in the property files are not fixed. If a shared property file contains errors, then
every component raises an alarm about the problem. The validation alarms are
warnings so they do not have to be cancelled manually after fixing the configuration.
For more information on the alarm, see section Alarm descriptions in the Alarms
document. For more information on accessing the trace logs, see section Trace logs in
the Troubleshooting Guide.
Steps
1 Log in to the AUI as a non operator-specific user with access rights to the Config-
uration files resource.
2 Click Configuration files in the vertical menu.

The Configuration files page opens. The list of files displays all configuration files in
directory /opt/profiler6/properties. On the cluster nodes, this directory actually
contains a link to the global filesystem where the files are stored.
DN70274664 Id:0900d80580528f10 145

Issue 5-0
Operating Guide
Figure 96 Configuration files
3 To open a configuration file for editing, click the name of the file.
4 The file will open in an editor view. Change the file as you wish, and click Save to
commit your changes.
For information on the configuration parameters in the files, see the Parameter Refer-
ence document. You can also use the search function of the NED documentation to
locate documentation that is relevant to the configuration parameters you are editing.
5 It is usually not necessary to manually restart the components affected by the

changes. Most components poll the files for changes.
6 After editing configuration files, you should check alarms history in AUI to detect
any configuration errors you may have made.
NPS will raise the 28821 CONFIGURATION INVALID warning if it detects any configu-
ration errors. Note that the automatic configuration validation does not protect against
all possible errors.
Further information
You may also edit the configuration files from the command line. To edit a property file,
login as the root user and open the file with a text editor (such as vi) from the directory
/opt/profiler6/properties.
146 Id:0900d80580528f10 DN70274664

Issue 5-0
Operating Guide
16.4 Viewing alarms

Clicking Alarms in the vertical menu of AUI will open the Currently open alarms page.
The Alarms link is only accessible to non operator-specific administrator users.
For a complete list of Nokia Siemens Networks Profile Server's alarms, see the NPS
application alarm descriptions chapter in the Alarms document. The document contains
a description of each alarm, as well as severity.
Figure 97 AUI - Currently open alarms page

On the Currently open alarms page, you see a list of open alarms. Each row of the list
contains the following data:
• ID - alarm ID
• Alarm text - the name of the alarm
• SEV - severity of the alarm, also indicated by the colour code of the alarm:
1. Critical (red background)
2. Major (orange background)
3. Minor (yellow background)
• SDN - System Distinguished Name, the originator of the alarm
• Date - when the alarm was generated
• Additional info - additional information of the event
• Cancel - button for cancelling the alarm
g Alarms with the severity Warning are not displayed on the Currently open alarms
page. They are only visible in the Alarm history page.
Clicking the Alarm history link will open the Alarm history page, which displays a history
of the alarm events. The format of the list is the same as for the currently open alarms,
except that there are no Cancel buttons.
DN70274664 Id:0900d80580547fe9 147

Issue 5-0
Operating Guide
Figure 98 AUI - Alarm history page
148 Id:0900d80580547fe9 DN70274664

Issue 5-0
Operating Guide Managing user rights
17 Managing user rights
17.1 Overview of user management

The management of Nokia Siemens Networks Profile Server (NPS) users in the Admin-
istration User Interface (AUI) is a part of the overall access right model of NPS. For a
description of the different accounts and access rights to the NPS system, please read
section Overview of access rights in the Administration Guide document.
As described in the Overview of access rights section, there is only one user account
that can create and manage the NPS user groups and users: the user admin. All oper-
ations on user groups and users must be performed by the admin account. There is one
exception; all users can change their own password.
User rights are managed on the user group level; the access rights of individual users
are determined according to their association with a user group. This means that before
you can create user account, you must create a user group with the access rights you
wish for the user to have.
For instructions on how to create, modify and delete user groups, see section Managing
user groups.
For instructions on how to create user accounts, see section Managing users.
17.1.1 Examples of user groups

Since the admin user is the only user account which is created after the installation,
there is immediately the need to create more accounts. This section presents example
access right configurations for typical user groups which can be created. The names of
the groups are not fixed; these are examples only.
Call center user group

There may be a need to create users that have a very limited access to the NPS
resources. For example, there may be a need to only allow the access to the subscriber
data of one operator, but deny all other access. This can be done by creating an
operator-specific user and allowing Read / Write access to the Subscribers &
Additional parameters resource:
g Limited access rights such as these are very suitable for applications that provision
subscriber data through the Profile Interface.
DN70274664 Id:0900d805806a2882 149

Issue 5-0
Managing user rights Operating Guide
Figure 99 User group example - Call Center user group
Network operator's administrator

The network operator may wish to create a user group which can access the system
management functions of AUI, and all operators and their subscribers. You cannot
150 Id:0900d805806a2882 DN70274664

Issue 5-0
create another admin account with superuser access, but you can create a non
operator-specific account with the maximum allowed access rights:
Figure 100 User group example - Network Operator admin
g As you can see from the figure above, it is not possible to grant access to user group
and account management functions. These resources are only accessible by the
admin user.
Operator-specific administrator group

Creating an operator-specific user group with maximum access rights will allow the
editing of that particular operator's operator settings, subscribers, subscriber types, and
MMS application profiles:
DN70274664 Id:0900d805806a2882 151

Issue 5-0
Managing user rights Operating Guide
Figure 101 User group example - Operator admin
MMS application administrator group

You can also create a user group that is specific to an MMS application. This allows the
creation of user accounts that are limited to managing the distribution lists that are
specific to this MMS application.
g The MMS application administrators cannot change the settings of their MMS appli-
cation.
152 Id:0900d805806a2882 DN70274664

Issue 5-0
Figure 102 User group example - MMS application admin
DN70274664 Id:0900d805806a2882 153

Issue 5-0
Operating Guide
17.2 Managing user groups

Purpose
To create, modify or delete Nokia Siemens Networks Profile Server (NPS) user groups,
follow the instructions below.
Before you start

Before creating or modifying user groups, you should be familiar with the access control
model of NPS. Read section Overview of access rights in the Administration Guide
document before proceeding.
Steps
1 Log in to the Administration User Interface (AUI) as user admin.
2 Click User groups in the vertical menu.

The User groups page opens, with a list of currently existing user groups. From this
page you can proceed to create new groups, edit the access rights of existing groups,
and delete groups.
Figure 103 User groups
3 To create a new user group, click New.

a) On the New user group page, enter a name and description for the group.
154 Id:0900d80580547ff6 DN70274664

Issue 5-0
Operating Guide
Figure 104 New user group

b) To create a user group which can only access the data for a particular operator,
select the Operator specific radio button, and select an operator from the drop-
down list.
Also remember that limiting the group to a certain operator will affect the access
rights of the group. Operator-specific groups cannot access system management
functions or edit other operators. For more information, see section Overview of
access rights in the Administration Guide document.
c) To create a user group which can only access the distribution lists of a particular
MMS application, select the MMS application specific check box, and select the
MMS application from the drop-down list.
If the desired MMS application is not visible in the drop-down list, select the operator
that owns the MMS application from the operator drop-down menu.
d) Click Create.
e) On the User group details page, assign access rights to NPS resources by marking
resources Read / Write, Read or Denied. Operator-specific user groups cannot be
granted access rights to any system management resources, or the rights to view
and edit other operator entities.
When users of the group log in to the AUI, they will only see the links to resources
to which they have at least Read access.
DN70274664 Id:0900d80580547ff6 155

Issue 5-0
Operating Guide
Figure 105 User group details

f) When you have granted the access rights, click Update to commit the changes.
4 To edit a user group, click its name in the list on the User groups page.
The User group details page for the group opens. Edit the access rights as required,
and click Update to commit the changes.
5 To delete a user group, select its check box in the Delete column and click the
Delete button.
g It is only possible to delete a user group if it has no users. If there are users, you will
receive an error stating that a child entity exists. If you still wish to delete the group,
you must delete all of its users first.
156 Id:0900d80580547ff6 DN70274664

Issue 5-0
Operating Guide
17.3 Managing users

Purpose
To create, modify, or delete Nokia Siemens Networks Profile Server (NPS) user
accounts, follow the procedure below.
Steps
1 Log in to the Administration User Interface (AUI) as user admin.
2 Click User accounts in the vertical menu.

The User accounts page opens with a list of currently existing user accounts. From this
page you can proceed to create new accounts, change the passwords and expiration
dates of existing accounts, and delete accounts.
Figure 106 User accounts
3 To create a new user account, click New.

On the New user account page, enter the following information for the new user
account:
• User name: The name of the user account. Used when logging in to NPS.
• Password: Enter the password for the user account.
• Confirm password: Re-enter the password here for verification.
• Password expiration date: If desired, you can set the password to expire on a
given date. The date format is dd.mm.yyyy hh:mm.
• User group: Select the user group from the drop-down menu.
When done, click Create.
DN70274664 Id:0900d805806a2884 157

Issue 5-0
Operating Guide
Figure 107 New user account
g The rules and configurations applied to administrate user passwords are described
in the section Password policy in the Administration Guide.
4 To change the password for a user account, click on the name of the account.
On the User account details page, click Change. In the Change password popup, enter
the new password (twice for confirmation) and click Change.
After changing the password, click Close.
158 Id:0900d805806a2884 DN70274664

Issue 5-0
Operating Guide
Figure 108 User account details - Change password
g When logged in the AUI, the user can enter the password change page by clicking
the user name link at the top of the AUI window.
5 To delete a user account, select its check box in the Delete column and click the
Delete button.
DN70274664 Id:0900d805806a2884 159

Issue 5-0
Operating Guide
17.4 Changing a network element password

Purpose
The following pre-configured network element accounts are created during Nokia
Siemens Networks Profile Server (NPS) installation:
• AG for Nokia Siemens Networks Application Gateway 3.0
• CA for Nokia Siemens Networks Content Analyzer
• DLS for Nokia Siemens Networks Delivery Server
• GGSN for Gateway GPRS Support Node
• GPFAPI for Generic Profile Fetch API
• ISD for the ICD Service Database
• MMSC for Nokia Siemens Networks MMS Service Center
• NBG for Nokia Siemens Networks Browsing Gateway
• NPM for Nokia Siemens Networks Profile Manager
• Presence for Nokia Siemens Networks Presence Server
• SMSC for Nokia Siemens Networks SMS Center
• TA for Nokia Siemens Networks Traffic Analyzer
• VOIP for Nokia Siemens Networks VoIP Server
The network elements and clients connect using the access rights of these accounts.
You cannot change the access rights or create/delete network element accounts, but
you can change the password.
The default password for each of the network elements is the same as the network
element name. For example, the defaults NPM username is NPM and the password is
NPM.
Steps

You must log in as a non operator-specific user with access rights to the Network
elements resource.
160 Id:0900d805806a2886 DN70274664

Issue 5-0
Operating Guide
2 On the Network elements page, click a network element name.
Figure 109 Network elements
DN70274664 Id:0900d805806a2886 161

Issue 5-0
Operating Guide
3 On the Network element details page, next to Password, click Change.
Figure 110 Network element details - change password
4 In the Change password popup window, enter the new password and click
Change.
The text in the popup will indicate whether the password change was successful or not.
5 The password for the network element entity is now changed. Depending on
which password you changed, you must perform additional configuration tasks
to make sure the connection is maintained:
• AG password
You must change the password supplied by AG as instructed in AG documentation.
• CA password
Even though the CA does not have to authenticate itself to the LDAP interface, the
LDAP interface uses the password internally. Define the new password in file
caldap.properties, by changing the value of the following parameter:
nap.ldap.pi.anonymous.access.password
The CA also uses this username/password pair to authenticate itself when connect-
ing to the Profile Interface. Change the password on the CA as instructed in the CA
documentation.
162 Id:0900d805806a2886 DN70274664

Issue 5-0
Operating Guide
• DLS password
Define the new password in file dls.properties, by adding the following param-
eter to the file:
nap.rfe.password=<password>
• GGSN password
Even though the GGSN does not have to authenticate itself to the LDAP interface,
the LDAP interface uses the password internally. Define the new password in file
ggsnldap.properties, by changing the value of the following parameter:
• GPFAPI password
Define the new password in file gpfapi.properties, by adding the following
parameter to the file:
nap.rfe.password=<password>
Profile Server uses the password defined in this property to authenticate the con-
necting GPFAPI client; the client does not have to supply this password.
• ISD password
If you are using the ISD service data tool, you must define the new password in the
file Define the new password in the file
/opt/profiler6/tools/isd/isdservicedatatool.properties, using
the property nap.util.isd.pi.password.
• MMS Center password
a) Change the password in the wrapper property file on the MMS Center. The file
is/opt/nokia/<wrapper>/<wrapper>.properties. Replace <wrapper>
with the name of the wrapper version you are using (for example, wrapper4).
The password is defined by the following property:
nap.wrapper.<mmsc_version>.password=<password>
For example, the property for wrapper31 (used with MMS Center 3.1) is:
nap.wrapper.mmsc31.password=<password>
• NPM password
You must change the password supplied by NPM as instructed in NPM documenta-
tion.
• Presence password
You must change the password supplied by the Presence Server as instructed in
Presence Server documentation.
• SMSC password
You must change the password supplied by the SMS Center as instructed in SMSC
documentation.
• TA password
Even though the TA does not have to authenticate itself to the LDAP interface, the
LDAP interface uses the password internally. Define the new password in file
taldap.properties, by changing the value of the following parameter:
• NBG password
If the LDAP anonymous access is allowed, define the new password in the
nbgldap.properties file by changing the value of the following parameter:
• VOIP password
You must change the password supplied by the VoIP Server as instructed in NVS
documentation. The password used with the bind DN (username)
DN70274664 Id:0900d805806a2886 163

Issue 5-0
Operating Guide
ou=SIPSubs,dc=noklab,dc=net, is checked against the password of network

element name VOIP.
164 Id:0900d805806a2886 DN70274664

Issue 5-0
Operating Guide Managing hunting gourps
18 Managing hunting gourps
18.1 Overview of hunting groups management

Nokia Siemens Networks Profile Server (NPS) provides several interfaces for managing
the hunting groups in the database. The bulk of the operations on hunting groups should
naturally be performed using the various data provisioning interfaces, but the Adminis-
tration User Interface (AUI) is more convenient to manage hunting groups infrequently.
For instructions on how to manage hunting group on AUI, see the following sections:
Creating a hunting group
Modifying a hunting group
Deleting a hunting group
For instructions on how to create/modify/delete members of hunting group, see section
Modifying a hunting group.
DN70274664 Id:0900d805806a288b 165

Issue 5-0
Operating Guide
18.2 Creating a hunting group

Purpose
The following procedure describes how to create a hunting group on AUI.
Steps
1 Log in to AUI as a user with access to the hunting group.
2 Click Hunting Groups in the vertical menu. The Hunting Groups page opens.
Figure 111 AUI – Hunting Groups page
3 On the Hunting Groups page, click New. The New group page opens.
Figure 112 AUI - New group page
4 Enter the value for each filed of the new hunting group, and then click Create.
• Group ID (MSISDN) Ringing group number. This number belongs to one of the
ringing group member. This value is mandatory.
• VMS Number VMS (diverted-to) number.
166 Id:0900d805805480da DN70274664

Issue 5-0
Operating Guide
• Sequential alerting time Indicates how many seconds will the alert last for sequential
processes.
• Parallel alerting time Indicates how many seconds will the alert last for parallel
hunting processes.
• Group IMSI IMSI number of the group.
• Alerting for data Alerting method for data calls.
• Connected Number Treatment Indicator Number treatment indicator.
• Alert method type Alerting method for non-data calls.
• Tone type Flag for indicating simple tone or ring back tone.
• User type Type of users.
5 The data of new hunting group is show on the Group-general page.
Figure 113 AUI – Hunting Group general

The detailed information of the Hunting Group general page is described in
18.3 Modifying a hunting group
Result
The new hunting group has now been created.
DN70274664 Id:0900d805805480da 167

Issue 5-0
Operating Guide
18.3 Modifying a hunting group

Purpose
The following procedure describes how to modify a hunting group entity. The hunting
group entities are usually modified to maintain their members.
Steps
3 Search for the hunting group which need to be modified by clicking Search.
You can narrow the search by entering group ID which supports wildcards. All searching
results will be listed on the Hunting Groups page.
Figure 114 Searching result
168 Id:0900d805806a28e2 DN70274664

Issue 5-0
Operating Guide
4 To modify the hunting group, click the hunting group ID on the hunting groups
list. The Hunting Group general page opens.
Figure 115 AUI – Hunting Group general

In this page you can edit data of the existing hunting group and update it by clicking
Update, or you can delete the hunting group by clicking Delete. You can return to
Hunting Groups page by clicking Cancel.
5 To manage members of the hunting group, click Members. The Hunting Group
members page opens.
Figure 116 AUI – Hunting Group members page
1. Creating a member of the hunting group.
DN70274664 Id:0900d805806a28e2 169

Issue 5-0
Operating Guide
1.1 Click New on Hunting Group members page, New Member page opens.
Figure 117 AUI – New Member page

1.2 Enter the values for the new member, and then click Create.
▪ Member ID MSISDN of member. Member ID is mandatory and is exclusive
in the hunting group.
▪ LDAP prefix Prefix for differentiating the LDAP record of embedded ringing
groups if the member number is identical with the actual group
number. And LDAP prefix also represents an embedded group
at the same time.
▪ Hunting order The place of the member in the hunting list, value 0 means the
member shall not be alerted. The value can be any integer from
0 to 15.
▪ Service code Default basic service code for the group.
▪ Embed group enabled Indicates that MSISDN is also a gourp ID of another
hunting group.
▪ Call diversion enabled Call diversion treatment indicator. It indicates
whether call diversion is allowed for the member. The true value
(suppressed) takes effect only when the FN306 Call Forwarding
Override optional feature is supported.
▪ Data primary enabled Indicates wether the member is the primary target for
data calls.
▪ Forwarding interrogation enabled Forwarding interrogation controls whether
call diversion information from HLR is fetched during groups
(using ATI) or member interrogation (using SRI).
g The single group can contains maximum 15 members only.
1.3 The new member of the hunting group has now been created.
2. Modifying or deleting a member of the hunting group.
2.1 Click the link of an existing Member ID which you want to modify on Hunting
Group members page. Update Member page opens.
170 Id:0900d805806a28e2 DN70274664

Issue 5-0
Operating Guide
Figure 118 AUI – Update Member page

In this page you can edit data of the existing member and update it by clicking
Update, or you can delete the member by clicking Delete.You can return to
Hunting Group members page by clicking Cancel.
DN70274664 Id:0900d805806a28e2 171

Issue 5-0
Operating Guide
18.4 Deleting a hunting group

Purpose
The following procedure describes how to delete a hunting group. Remember that the
hunting group cannot be deleted when contains any members. That means all members
of the hunting group should be deleted before deleting the hunting group entity.
Steps
3 Search for the hunting group that you want to delete by clicking Search.
You can narrow the search by entering group ID which supports wildcards. All searching
results will be listed on the Hunting Groups page.
4 Click the selected hunting group ID on the hunting groups list. The Hunting Group
general page opens.
5 Delete all members in the hunting group.

Select all the members that you want to delete,and then click Delete.
6 After all members have been deleted, click Delete on the top right corner to delete
the hunting group.
172 Id:0900d805805480db DN70274664

Issue 5-0

NPS Operating Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NPS Operating Guide

Uploaded by

Copyright:

Available Formats

Nokia Siemens Networks

Profile Server, Rel. 6.1.4,

Operating and maintaining instructions

f Important Notice on Product Safety

The same text in German:

1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Operating the Profile Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4 Managing subscriber types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.3.6 Subscriber type - VoIP Server preferences . . . . . . . . . . . . . . . . . . . . . . 44

8 Managing MMS application profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

9.2.2 Managing existing lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

10 Managing NTMS groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

11 Managing terminal models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

12 Overview of SMSC configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

13 Managing additional parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

14 Subscriber activity management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

16 System management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

17 Managing user rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

18 Managing hunting gourps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Figure 46 AUI - Subscribers page with result list . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Figure 93 Component details page for LICAUTH_1 component. . . . . . . . . . . . . . 142

1 About this document

1.2 Summary of changes

Date Issue Summary of changes

Date Issue Summary of changes

2 Operating the Profile Server

2.1 Browser requirements

2.2 Accessing the AUI

Figure 1 AUI login page

2.3 Basic AUI functions

Figure 2 AUI main page

2.3.1 Entering data

2.3.2 Changing the password and viewing access rights

Figure 3 Current user - change password

Figure 4 Current user - access rights (partial)

2.3.3 Accessing the user interfaces of other network elements

2.3.4 Accessing documentation

2.3.5 Viewing the About page

2.4 Logging out

3.1 Overview of operator management

3.1.1 Access rights for managing operators

3.2 Creating an operator

3.2.1 Creating an operator

Before you start

2 Click Operators in the vertical menu.

Figure 5 New operator page

The following characters are not allowed in the VOId:

" (quotation) % (percentage)

Table 1 Illegal characters in operator ID (VOId)

Examples of valid VOId strings:

6 Click Add to open a field for an operator resolution rule.

7 When done, click Create.

3.2.2 IMSI/MSISDN range validation in provisioning

resolvedVOCheck.enabled rejectWhenVONotFound Own Not VO not

Table 2 Range validation with different configurations

MSISDN/MDN VOId Result

3.3 Modifying an operator

3.3.1 Selecting the operator

Figure 6 Operators page

3.3.2 Operator details

Figure 7 Operator - details page

3.3.3 Operator - MMS Details

• Update MMS terminal capability in originator MMS profile fetch