You are on page 1of 21

MSC Server, Rel. M16.

2,
Feature Documentation,
version 2
Feature 1907: One Number Service

DN70665442
Issue 2-1-0

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of
its products and services. We would like to encourage you as our customers and users to join
us in working towards a cleaner, safer environment. Please recycle product packaging and
follow the recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental
services we offer, please contact us at Nokia Siemens Networks for any additional information.

Feature 1907: One Number Service

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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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 2013/12/21. All rights reserved

Important Notice on Product Safety


This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the Legal, Safety
and Environmental Information part of this document or documentation set.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit


Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,
Safety and Environmental Information dieses Dokuments oder dieses Dokumentationssatzes.

Id:0900d8058096911c

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

Table of Contents
This document has 21 pages.
1
1.1
1.2
1.3
1.3.1
1.3.2
1.3.3
1.4
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
1.4.6
1.4.7
1.4.8
1.4.9
1.4.10
1.4.11
1.5
1.6
1.7
1.8
1.9
1.9.1
1.9.2
1.10
1.11

Feature 1907: One Number Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Benefits for the operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Requirements for using the feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Ringing group inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Ringing group record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Alerting methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Ringing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
One Number Service and Common CLI . . . . . . . . . . . . . . . . . . . . . . . . 12
LDAP based Common CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
One Number Service, high availability and Read failure measurement. 13
Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Related and interworking features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Operator interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
MMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Subscriber interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
External interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Main changes in Feature 1907: One Number Service. . . . . . . . . . . . . . 20

DN70665442
Issue 2-1-0

Id:0900d8058096911c

Feature 1907: One Number Service

List of Figures
Figure 1
Figure 2

The ringing group inquiry is performed in the NVS . . . . . . . . . . . . . . . . . . 9


The ringing group inquiry is performed in the GMSS . . . . . . . . . . . . . . . . 9

Id:0900d8058096911c

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

List of Tables
Table 1
Table 2

DN70665442
Issue 2-1-0

The meaning of the alerting method for speech calls . . . . . . . . . . . . . . 11


Correlation between the alerting method and the primary member for the
data calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Id:0900d8058096911c

Feature 1907: One Number Service

Id:0900d8058096911c

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

Feature 1907: One Number Service

1 Feature 1907: One Number Service


1.1

Introduction
The One Number Service (ONS) builds on those MultiSIM features already employed
by the Nokia Siemens Networks MSS and the Nokia Siemens Networks Mobile VoIP
Server (NVS). However, one major difference between ONS and the MultiSIM functionality found in the MSS and NVS is that ONS does not require a DX HLR network element
to function. Instead, the ONS uses the LDAP directory framework to store MultiSIM, that
is, ONS group data.

The terms MSIM and MultiSIM used in an LDAP environment always refer to the One
Number Service functionality.
Another difference between ONS and the already existing MultiSIM functionality in MSS
and NVS solutions is the group size: ONS supports more members per single ringing
group15 to be exact. This makes it a better choice in Small Office, Home Office
(SOHO) environments.
One Number Service supports the selection of CLI presentation by the means of preanalysis.
This feature is supported by both the MSS and the NVS.

1.2

Benefits for the operator


This feature provides the following benefits:

1.3
1.3.1

Alternative solution for MultiSIM deployments that uses the Lightweight Directory
Access Protocol (LDAP) directory framework to store ONS group data.
The maximum number of members in a single ringing group is increased to 15.
The logic for multiradio terminal (MRT) users is enhanced and separated from
normal MultiSIM user behavior.
Member call diversion handling is defined at a member level.

Requirements for using the feature


Software
With configuring One Number Service functionality, the following features are automatically activated:

Feature 1576: Parallel Alerting for MultiSIM service


Feature 1545: Sequential Alerting for MultiSIM service
Feature 1841: Service Attribute Analysis
Feature 1620: IN Attribute Analysis
Feature 1670: SIP Subscriber Database

This feature requires the use of the following protocol:

DN70665442
Issue 2-1-0

Lightweight Directory Access Protocol (LDAP)

Id:0900d80580969116

Feature 1907: One Number Service

Feature 1907: One Number Service

The Common CLI functionality interworks with the One Number Service functionality.
Feature 1541: Same CLI for Multiple Subscribers must be purchased separately, and it
requires DX HLR as a network element.

1.3.2

Hardware
This feature has no special requirements for hardware.

1.3.3

Products
This feature functions in the following Nokia Siemens Networks network elements:

1.4

MSC Server (MSS)


Home Location Register (HLR)
Nokia Siemens Networks Profile Server (NPS)
3rd party products as long as they support the MSS/NVS LDAP interface and the
specific multisim.schema required for this feature.

Functionality
The One Number Service allows a call, made to a ringing group number, to be branched
to all members of that group, either in a round-robin fashion or simultaneously to all
members at the same time.
This feature introduces the following additional components to the NVS and MSS/VLR:

Enhanced LDAP schema containing ringing group data


Sequential and parallel ringing service logic in the gateway MSS (GMSS), without
HLR support
Support for single, multiple, and multiradio terminal user types
Additional statistic counters

Ringing group related data is stored in the LDAP ONS database. The MSISDN identifier
of the record represents the ringing group number. The members of the ringing group
are defined in an MSISDN list. The group can have up to fifteen members. Group
members must have their own unique MSISDN number. One group members MSISDN
can be identical to the ringing group number.
Ringing group member MSISDNs can represent subscribers equipped with terminals
that have different types of access, like GSM, UMTS, SIP, MRT, or even fixed.
When the speech call is routed to the NVS or to the GMSS, it performs the usual HLR
inquiry. If the target of the call is a ringing group, then the GMSS executes the LDAP
query to get the ordered list of the own MSISDNs of the group members. The GMSS
initiates its internal service for sequential or parallel alerting, where the call is tried to be
connected toward the members of the group. The members of a ringing group are interrogated with separate SRI MAP operations, and the call is routed towards its destination.

In ONS messaging scenarios, only parallel and sequential hunting are allowed.
In both call and messaging scenarios, group in group configurations are allowed.
However, in messaging scenarios, the group MSISDN cannot be identical to the
MSISDN of any member in the group. Hence, when enhanced ONS for messaging is
activated, the usage of the LDAP prefix member attribute is not supported.

Id:0900d80580969116

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

1.4.1

Feature 1907: One Number Service

Ringing group inquiry


ONS
+
SDB
LD
AP

M
AP

HLR

1.SETUP (RGN)

2.IAM (MSRN_A)

MSS/
NVS

MS A

4.REL

3.SETUP
(MSISDN A)

5.INVITE
(SIP URI A)

2.INVITE
(SIP URI B)

MRT A

MS B
Figure 1

VMSS

The ringing group inquiry is performed in the NVS

Figure 1 shows a network element level example, when the ringing group inquiry is performed in the NVS. Parallel alerting takes place to a ringing group of two members: the
first is an MRT, and the second is a SIP subscriber.

ONS
+
SDB

1.SETUP (RGN)

LD

AP

MS A

LD

AP

HLR

3.IAM (MSRN_A)

GMSS
2.SETUP
(MSISDN B)

MSS/
NVS

2.SETUP
(MSISDN A)

MS B
Figure 2

AP

4.INVITE
(SIP URI A)

MRT A

The ringing group inquiry is performed in the GMSS

Figure 2 shows a network element level example, when the ringing group inquiry is performed in the GMSS. Parallel alerting takes place to a ringing group of two members:
the first is an MRT, and the second is a CS subscriber.

1.4.2

Ringing group record


Group level information
The ringing group record contains the following:

DN70665442
Issue 2-1-0

Id:0900d80580969116

Feature 1907: One Number Service

Feature 1907: One Number Service

Group number
Member numbers
A maximum of 15 members per group is supported.
Voice Mail System (VMS) (diverted-to) number
Connected number treatment indicator
The indicator controls the connected party number presentation to the calling party.
The connected party number can be either the group number or a member number.
The presentation can be allowed or restricted.
Alerting method
Alerting method can be defined for data calls and non-data calls independently.
The following alerting methods are possible:
not defined
sequential
parallel
parallel preferred
intelligent
Alerting time for different hunting methods (sequential and parallel)
User type
The user type can be the following:
single
multiple
MRT
Tone type
The flag indicates if simple tone or ringback tone (bool parameter) is played by the
internal service logic. The flag is only relevant in parallel hunting scenarios.
Default basic service code
When the call type cannot be determined from the available information received
from the setup or the HLR, this service code is responsible for verifying the configured alerting method.

Member level information


Each member field can contain the following attributes:

10

Embedded group indicator


The indicator identifies a group in group scenario. That is, if the member of the group
represents a separate (embedded) ringing group by itself.
LDAP prefix member attribute
The prefix differentiates the embedded ringing group LDAP record if the member
number is identical with the actual group number. It also represents an embedded
group at the same time.
Call diversion treatment indicator
It indicates if call diversion is allowed for the member. The true value (suppressed)
is valid only if optional Feature 306: Call Forwarding Override is supported.
Hunting order
This is the place of the member in the hunting list. Value 0 means that the member
is not alerted. It is recommended to properly define the hunting order even in the
case of parallel hunting groups.
Indication if the member is primary target for data calls

Id:0900d80580969116

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

Feature 1907: One Number Service

Alerting method in LDAP

Speech call

Not defined

sequential

Sequential

sequential

Parallel

parallel

Parallel preferred

parallel

Intelligent

intelligent

Other

sequential

Table 1

Alerting method in
LDAP

The meaning of the alerting method for speech calls

Primary member defined

Primary member not defined


Bit-transparent data call Other types of data call

Not defined

primary alerted

sequential

sequential

Sequential

primary alerted

sequential

sequential

Parallel

primary alerted

parallel

configuration: release call


or group MSISDN alerted
or first member alerted

Parallel preferred

primary alerted

parallel

sequential

Intelligent

intelligent

intelligent

intelligent

Other

primary alerted

sequential

sequential

Table 2

Correlation between the alerting method and the primary member for the data calls

1.4.3

Alerting methods

DN70665442
Issue 2-1-0

Sequential alerting
With sequential alerting, a call is terminated to a ringing group number by attempting
the ringing group members sequentially. If the alerted member of the ringing group
does not answer, then the next member of the ringing group is tried. Only one
member of the ringing group is attempted at a time.
Sequential alerting is complete when an answer is received from the alerted phone
or there are no more members to alert. Sequential alerting does not affect the ability
of a member to originate a call, but it may affect the ability of a member to receive a
call.
Parallel alerting
With parallel alerting, the first answering leg is connected to the calling party, the
other legs are released. Other mobile-terminated transactions are delivered only to
a dedicated member called primary member. The parallel ringing service is applicable only to voice and bit-transparent data calls.
Intelligent hunting
Intelligent hunting is controlled by SCP.

Id:0900d80580969116

11

Feature 1907: One Number Service

Feature 1907: One Number Service

Based on the received alerting method, the GMSS initiates the corresponding control
logic for alerting the members.
The input parameters for the control logic are the following:

1.4.4

members list
user type
no answer time
call forwarding suppression indication
ringback tone indication
diverted-to number
LDAP suppression
embedded group indication
LDAP routing prefix

Ringing service
The ringing service can be offered to single, multiple or MRT users. The user type can
be selected on a ringing group base. The main difference between the user types are
the following:

1.4.5

Single cases
Alerting is finished and the diverted-to number is connected when busy information
is received in the backward release message.
MRT case
It is similar to the single case. In addition, alerting is finished already when the
alerted member does not answer the call.
Multiple user case
When a backward release is received with busy information from a leg, the other
members are also alerted.

One Number Service and Common CLI


The One Number Service functionality is a terminating service where subscribers are
grouped under one common number, that is, under a group MSISDN. The ONS functionality does not provide a Common CLI solution as such for the originating service.
However, ONS does interwork with the common CLI originating service in the following
scenarios if prerequisites are met:

12

In a network with or without NVS where DX HLR is deployed.


In this environment, Feature 1541: Same CLI for Multiple Subscribers has to be activated.
In a network with NVS where multivendor HLR is deployed.
In an NVS environment, the common CLI can be provisioned only for SIP subscribers in the SIP Subscriber Database (SDB) of the LDAP Server. Hence, a SIP subscriber provisioned for ONS can also be provisioned for common CLI.
However, if an ONS group has more than one CS 2G/3G members, the common CLI
will not apply to those CS members. The only exception is the scenario where a CS
member number is also the group number that is, the member MSISDN is identical to the group MSISDN. In this provisioning scenario, the member needs no
separate common CLI.

Id:0900d80580969116

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

Feature 1907: One Number Service

The problem of missing common CLI for CS members can be overcome by applying
an originating SCP service providing common CLI for the members.
With extended preanalysis, it is also possible to configure what number, that is,
which CLI is used at the originating side of call setup.

In IMS environment, where the NVS functions in Application Server mode with Sh
connectivity to the HSS, the common CLI must also be provisioned to the SIP-BasicData in the HSS.
For more information on CLI, see section Selecting CLI in Feature 1907: One
Number Service, Feature Activation Manual.
For more information on the SIP Subscriber Database, see NVS and MSS LDAP
Interface Description and Feature 1670: SIP Subscriber Database, Feature Description.
For more information on SIP-Basic-Data, see Feature 2027: Sh for NVS Subscriber
Repository, Feature Description and Sh Interface Description.

1.4.6

LDAP based Common CLI


The Common CLI solution can be defined for CS members in the DX HLR, for SIP
members in the NPS.
The Common CLI configured in the DX HLR is available separately from the One
Number Service by activating Feature 1541: Same CLI for Multiple Subscribers.
The Common CLI configured in the NPS is available as part of the One Number Service
or by activating the LDAP based common CLI functionality with the dedicated license.
The LDAP based common CLI functionality enables the operator to define an additional
MSISDN, a so called Common CLI in the SIP profile of the subscribers. If this Common
CLI is recognized by the MSS in a SIP originated call, it is chosen as the presentation
number for the calling party by default. Optionally, the normal subscription MSISDN can
be used as the additional calling party number.
If the LDAP based common CLI functionality is activated with a license, then UTPFIL
parameter controls, whether

g
1.4.7

the MSS uses the subscription's own CLI as the additional calling party number in
the outgoing IAM at all.
the MSS uses the subscription's own CLI as the additional calling party number in
the outgoing IAM only if no additional CLI is received from the SCP.
the MSS always uses the subscription's own CLI as the additional calling party
number in the outgoing IAM even if an additional CLI is received from the SCP.

If the Common CLI is defined for a subscriber in the DX HLR or in the NPS, then it is
used as the calling party number by the MSS. Therefore the CDRs contain this common
CLI in the calling party address field.

One Number Service, high availability and Read failure measurement


One Number Service data can be managed and maintained by LDAP solutions, such
as, NPS, One-NDS or OpenLDAP. The ONS database is an LDAP directory. The ONS
data, residing in the LDAP directory, is accessed and queried by the LDAP client pro-

DN70665442
Issue 2-1-0

Id:0900d80580969116

13

Feature 1907: One Number Service

Feature 1907: One Number Service

cesses of the MSS/NVS. The client processes are located in the signalling units of the
MSS/NVS.
The MSS/NVS supports both the two-site and the three-site LDAP client-server model,
that is, LDAP server deployment on two or three sites. The optional high availability
model offers a more flexible management of the LDAP databases in primary, secondary
and tertiary servers. The high availability three-site model is an optional functionality and
is controlled by license.
If both the primary and secondary servers fail, the tertiary server can continue serving
LDAP requests. Read failure measurement functionality provides an optimized solution
to manage client-side high availability. Read failure measurement is an optional functionality and is controlled by license.
For more information on LDAP database and LDAP server configuration, see LDAP
User Guide for NVS and MSS.
For more information on the configuration of LDAP client processes, see Subscriber
Profile Database Configuration Administration Handling, JD Command Group.
For more information on the high availability three-site model and Read failure measurement functionality, see the respective sections of the LDAP User Guide for NVS and
MSS.
For more information on option control, see sections LDAP model and LDAP client applications of the LDAP User Guide for NVS and MSS.

1.4.8

Files
This feature does not affect any files that are directly visible to the operator.

1.4.9

Parameters
User type selection and call processing
SEQ_ALERT_USER_TYPE (002:0826)
This PRFILE parameter controls user type selection. The user type can be single,
multiple or multiradio user. In the case of single user type, the condition can be set if the
last member is alerted or if the call is released when the busy condition is met.
INSTR_FOR_RGENQ_FAILURE (007:0318)
This PRFILE parameter controls call processing when the ringing group inquiry fails for
some reason.
INSTR_FOR_PRH_VS_CSD (007:319)
This PRFILE parameter controls call processing for the failure case where parallel
hunting cannot be continued due to non bit-transparent data call, which is not supported
by parallel hunting method.
LDAP connection and LDAP query
LDAP_ENQUIRY_TIMER (002:1574)
This PRFILE parameter indicates the time in 1/100th of a second that the MSS/NVS
waits for the response of the LDAP ONS query.

14

Id:0900d80580969116

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

Feature 1907: One Number Service

LDAP_CONN_UNIT (002:1572)
This PRFILE parameter defines which unit should create the LDAP connection. The SIP
Call Processing Unit (SCPU) always creates the LDAP connection and this parameter
has no effect on it. By setting this parameter, operator controls and determines whether
the SIGU or CCSU creates the connection to the LDAP server.

1.4.10

Statistics
The MSC observation report can display the increased group of fifteen members. The
alerting method and the ringing group number is displayed the same way as earlier.
However, there are additional counters for the newly introduced members both in the
ASCII and the XML report.

1.4.11

Charging
This feature has no effect on charging.

1.5

Capacity

CPU and MB capacity


The use of this feature brings increase in the size of the observation report message.
Due to the increased message size the load of message bus is also increasing.
Link capacity
This feature has no effect on Link capacity.
I/O capacity
This feature has no effect on I/O capacity.
Process and resource considerations
The size of the statistical call file (SCALLF) is increased due to the increased
number of the group members. This also increases the memory requirements.

The LDAP query has no significant effect on the capacity as the size of 1 LDAP query
is 5 kbyte.

1.6

Restrictions
The following restrictions must be considered when using this feature:

DN70665442
Issue 2-1-0

On-line call monitoring (OLCM) activation must be set for the members. In case of
the whole group, the setting must be done for all members.
The IN services defined on group level are always suppressed.
Member service synchronization
Since the core characteristic of ONS is storing group data in LDAP, the group
settings in LDAP determine and overrule the behavior of the member subscribers.
Thus, the member level service settings that may be assigned in the HLR do not take
affect in the case of ONS.
One Number Service functionality always requires an LDAP Server. Although VoIP
subscriber data (SDB) can be provisioned to the HSS, group data provisioning
(including member list) is only supported in the LDAP Server. Therefore, in IMS environment, where the NVS functions in Application Server mode, and the VoIP subscriber data (SDB) is stored in the HSS, the LDAP Server is still required. Otherwise,
One Number Service functionality is not supported.

Id:0900d80580969116

15

Feature 1907: One Number Service

g
1.7

Feature 1935 has the following characteristics:


In messaging scenarios, only parallel and sequential hunting are allowed.
In both call and messaging scenarios, group in group configurations are allowed.
However, in messaging scenarios, the group MSISDN cannot be identical to the
MSISDN of any member in the group.
Hence, when enhanced ONS for messaging is activated, the usage of the LDAP
prefix member attribute is not supported.
When both Feature 1907 and Feature 1935 are activated, certain configuration procedures have to be followed. For more information, see Feature 1907: One Number
Service, Feature Activation Manual.

Related and interworking features

1.8

Feature 1907: One Number Service

Feature 234: Completion of Calls to Busy Subscriber


In the case of a ringing group terminated call, the CCBS possible indicator is
changed to CCBS not possible.
Feature 1545 and Feature 1576: Sequential and Parallel Alerting (MultiSIM services)
The MultiSIM feature implements similar functionality but requires DX HLR support.
Feature 1570: Selective Ringback Tone
The One Number Service feature supports the Selective Ringback Tone (SRBT)
functionality. As a prerequisite, Feature 1570 has to be activated in the GMSS.
When using the One Number Service feature, Selective Ringback Tone usage is
applicable only when sequential alerting method is in use.
For parallel alerting, the SRBT functionality works with One Number Service without
the need for another interworking feature.
Feature 1935: MultiSIM Enhancement for SMS and NVS Messaging
The One Number Service for SMS and NVS Messaging functionality of Feature
1935 extends the call related One Number Service with SMS and NVS messaging
support. The enhanced functionality allows the delivery of SMs/SIP MESSAGEs to
all members of the group.
Feature 2027: Sh for NVS Subscriber Repository
Sh is a Diameter-based interface that functions between a Nokia Siemens Networks
Mobile VoIP Server (NVS), operating as a telephony application server (TAS) in an
IP Multimedia subsystem (IMS), and a Home Subscriber Server (HSS). Depending
on the network configuration, the NVS may retrieve the VoIP subscriber data (previously stored in the SDB LDAP directory) from the HSS for various purposes (miscellaneous registration scenarios, subscriber data restoration, user registration
inquiry).

Compliance
This feature is Nokia Siemens Networks proprietary.

16

Id:0900d80580969116

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

1.9
1.9.1

Feature 1907: One Number Service

Operator interfaces
MMLs
Extended Preanalysis Handling, CW Command Group
You can use the commands of the CW command group to create and maintain the
extended preanalysis.

CWRCREATE FINAL RESULT


CWSMODIFY FINAL RESULT

For more information on this command group, see Extended Preanalysis Handling, CW
Command Group.
Attribute Analysis Handling, RQ Command Group
You can use the commands of this command group to handle attribute analysis.

RQCCREATE SUBANALYSIS
RQMMODIFY SUBANALYSIS
RQDDELETE SUBANALYSIS
RQIINTERROGATE SUBANALYSIS
RQSCREATE INTELLIGENT NETWORK RESULT
RQVMODIFY INTELLIGENT NETWORK RESULT
RQPCREATE SERVICE RESULT
RQUMODIFY SERVICE RESULT
RQQINTERROGATE SERVICE RESULT

For more information on this command group, see Attribute Analysis Handling, RQ
Command Group.
Subscriber Profile Database Configuration Administration Handling, JD
Command Group
You can use the commands of this command group to configure and interrogate One
Number Service client configuration.

JDMCREATE OR MODIFY DIRECTORY SERVER CONFIGURATION


JDIINTERROGATE DIRECTORY SERVER CONFIGURATION
JDDDELETE DIRECTORY SERVER CONFIGURATION
JDSCHANGE THE STATE OF DIRECTORY SERVER CONFIGURATION
JDTDISPLAY THE LDAP CONNECTION TABLE OF A UNIT
JDYCOPY DIRECTORY SERVER CONFIGURATION

For more information on this command group, see Subscriber Profile Database Configuration Administration Handling, JD Command Group.

1.9.2

Alarms
This section briefly describes the alarms and disturbances that have an affect on the
feature. An alarm is active until it is cancelled or the unit is restarted. Alarms have priority
against disturbance, which means that if an alarm occurs for an erroneous case, the disturbance is not raised for the same failure.

DN70665442
Issue 2-1-0

Id:0900d80580969116

17

Feature 1907: One Number Service

Feature 1907: One Number Service

1361 A CONNECTION OF AN LDAP APPLICATION HAS FAILED


This disturbance indicates that a connection to a directory server application, like CNAP
or ONS, has failed. The disturbance contains the APPL and the SERVPRI attribute
values, the IP address and the remote port, so you can check the system for more information regarding the disturbances cause using the JDT command.
The failure_type is also given with these values. The failure_type can be either 0E, suggesting an LDAP level failure, or 0F, suggesting a TCP/IP level failure. The
failure_reason indicates the reason for the connection failure.
The disturbance is automatically cancelled by the system after its default alive time.
3658 A CONNECTION POOL OF AN LDAP APPLICATION HAS FAILED
This alarm indicates that a connection pool to a directory server application, like CNAP
or ONS, has failed. The alarm contains the APPL and the SERVPRI attribute values, so
you can check the system for more details regarding the alarms cause using the JDT
command.
The system cancels the alarm when the ratio of failed connections in the connection pool
drops below the limit of the preconfigured faulty connection threshold attribute for the
given LDAP application.
3659 ALL THE CONNECTION POOLS OF AN LDAP APPLICATION HAVE FAILED
This alarm indicates that all the connection pools for a particular directory server application, like CNAP or ONS, have failed. As a result, the corresponding LDAP application
data cannot be fetched from any of the LDAP directory servers.
Since the alarm contains the APPL attribute value, you can check the system for more
details regarding the alarms cause using the JDT command.
The system cancels the alarm when at least one of the failed connection pools for the
directory server application starts to work againthat is, moves to UP/ACTIVE state.
A more detailed description of these alarms and disturbances can be found in the
Product Information Center under the link Reference Information.
For more troubleshooting information, see subsection Troubleshooting of LDAP User
Guide for NVS and MSS.

1.10

Subscriber interfaces
This feature has no effect on the subscriber interface.

1.11

External interfaces
LDAP
This feature brings change to an already existing interface. The LDAP interface is
enhanced with the multisim.schema LDAP schema file towards the NPS or other
suitable LDAP database.
The multisim.schema schema file for the One Number Service subscriber data located
in the external LDAP server has been updated with messaging-specific attributes:

18

UsedForSMS
SMSHuntingOrder
SMSHuntingType

Id:0900d80580969116

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

Feature 1907: One Number Service

For more information on the multisim.schema LDAP schema file when One Number
Service is activated for messaging, see the corresponding Feature 1907: One Number
Service, Feature Activation Manual.
For more information about the LDAP interface and schema files, see NVS and MSS
LDAP Interface Description.

DN70665442
Issue 2-1-0

Id:0900d80580969116

19

Main changes in Feature 1907: One Number Service

Feature 1907: One Number Service

Main changes in Feature 1907: One Number


Service
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes made between issues 2-1-0 and 2-0-1
The following sections have been updated:

One Number Service and Common CLI


A note has been added on the provisioning of the common CLI to the SIP-BasicData repository data in the Home Subscriber Server (HSS).
Restrictions
Restriction has been added with regard to One Number Service functionality in IMS
environment.
Related and interworking features
Feature 2027: Sh for NVS Subscriber Repository has been added.

Changes made between issues 2-0-1 and 2-0-0


Editorial updates have been made throughout the document to reflect changes incurred
by the Nokia Siemens Networks portfolio.
Changes made between issues 2-0-0 and 1-0-2
The following section has been added to the document:

One Number Service, high availability and Read failure measurement

The following sections have been updated:

MMLs
The description of Subscriber Profile Database Configuration Administration Handling, JD Command Group has been updated.
Alarms
One disturbance and two alarms have replaced 1308 PRIMARY LDAP DIRECTORY SERVER ACCESS FAILED and 3312 LDAP DIRECTORY SERVER
ACCESS FAILED.

Section LDAP based Common CLI has been added to the document.
Changes made between issues 1-0-2 and 1-0-1
The following sections of the document have been updated with information on the interworking of ONS and Feature 1935: MultiSIM Enhancement for SMS and NVS Messaging:

Restrictions
Related and interworking features
External interfaces

The Ringing Group Database (RGDB) has been renamed to One Number Service
(ONS) database.
Changes made between issues 1-0-1 and 1-0
The following section has been added to the document:

20

One Number Service and Common CLI

Id:0900d80580969118

DN70665442
Issue 2-1-0

Feature 1907: One Number Service

Main changes in Feature 1907: One Number Service

Editorial changes have been carried out in the document.

DN70665442
Issue 2-1-0

Id:0900d80580969118

21