1 Introduction
This chapter contains general information about the organization of this guide and conventions used.
Overview
Local Number Portability (LNP) provides a user with the ability to move the telephone service from one service provider to another without changing the telephone number. LNP is managed by Number Portability Administration Centers (NPACs), which serve different geographical regions. NPACs distribute LNP data to local service management systems (LSMSs), which, in turn, distribute the LNP data to network elements, for example, EAGLE STPs. The LSMS keeps data for each NPAC region in a separate regional database. The data for any telephone number must be the same at the NPAC, the LSMS, and the network elements.
In addition, the LSMS stores locally provisioned data in a database separate from the regional databases and sends that data to all network elements. Locally provisioned data must also be the same between the LSMS and the network elements.
If the LNP databases of the LSMS and the network element get out of synchronization (for example, after an outage), the LSMS LNP database is used as the master database to synchronize the network element LNP database.
The LSMS and the network element use the following methods to synchronize their databases:
-
Resynchronizing - the LSMS resends all transactions to the network element up to a maximum number of transactions (automatic resynchronization) or a maximum period of time (optional user-initiated resynchronization).
-
Reconciling - after an audit of the network element LNP data, the user can reconcile any differences discovered during the audit.
-
Bulk Loading - complete replacement of the network element LNP database.
Scope and Audience
This manual is intended for anyone responsible for synchronizing the LNP database on the network element with the LNP database on the local service management system. Users of this manual and the others in the EAGLE family of documents must have a working knowledge of telecommunications and network installations.
Acronyms and Terminology
The following table lists the acronyms and the terminology used in the document:
Table 1-1 Acronyms and Terminology
| Acronym | Definition |
|---|---|
| CLLI | Common Language Location Identifier |
| DB | Database or Data bus |
| ELAP | EAGLE Local Number Portability Application Processor |
| EMS | Element Management System |
| HS | High Speed |
| LNP | Local Number Portability |
| LSMS | Local Service Management System |
| MPS | Multi-Purpose Server |
| NE | Network Element |
| NPAC | Number Portability Administration Center |
| PDP | Permissive Dialing Period, Power Distribution Panel, or Packet Data Protocol |
| RTDB | Real Time Database |
| TCP/IP | Transmission Control Protocol or Internet Protocol |
| UAM | Unsolicited Alarm Message |
Documentation Admonishments
Admonishments are icons and text throughout this manual that alert the reader to assure personal safety, to minimize possible service interruptions, and to warn of the potential for equipment damage.
Table 1-2 Admonishments
| Icon | Description |
|---|---|
 |
Danger: (This icon and text indicate the possibility of personal injury.) |
 |
Warning: (This icon and text indicate the possibility of equipment damage.) |
 |
Caution: (This icon and text indicate the possibility of service interruption.) |
 |
Topple: (This icon and text indicate the possibility of personal injury and equipment damage.) |
Manual Organization
The procedures described in this document are performed on Oracle Communications EAGLE LNP Application Processor (ELAP) 10.0 and higher.
This manual is organized into these sections:
-
Introduction contains general information about the organization of this manual.
-
LNP Database Synchronization Overview presents an overview of the various methods available, depending on the features installed, for synchronizing the LNP database on the network element (NE) with the LNP database on the Oracle Communications LSMS.
-
Managing Resynchronization from the LSMS describes how automatic re-synchronization (which re-sends all transactions previously sent from the LSMS to the NE up to a maximum number of transactions) occurs and how to manage from the LSMS optional, user-initiated re-synchronization (which re-sends all transactions that were previously sent from the LSMS to the NE over a period of time not to exceed seven days)the re-synchronization.
-
Choosing a Database Maintenance Procedure describes the notifications that let you know that manual intervention is required when automatic re-synchronization of the LNP databases cannot be accomplished, and guides you in choosing the most appropriate and efficient synchronization procedure, depending on the features installed at the LSMS and at the NE.
-
Auditing and Reconciling Network Elements from the LSMS describes how to audit network element data. At any time, unless certain conditions exist, an audit of the subscription data contained on the network element can be initiated from the LSMS. An audit compares the subscription version data at the network element with that at the LSMS.
-
Managing Bulk Load from the LSMS describes how to initiate and manage an electronic bulk download at the LSMS. Bulk loading completely replaces an LNP database (all subscription version, NPA Split, Translation Type Service, default Global Title Translation and override Global Title Translation data) at a network element.
-
Copying One RTDB from Another RTDB describes how to copy the contents of the Real-Time Database (RTDB) that exists on the mated Oracle Communications EAGLE LNP Application Processor (ELAP) server to an RTDB within the same network element that needs database restoration or to copy the contents of the RTDB that exists on an ELAP on the mated network element to an RTDB that needs database restoration.
-
Distributing the LNP Database after LSMS-Based Operation or RTDB Copy describes how the user distributes to all the Service Modules in the network element the NE LNP database that has been changed as a result of an LNP Database Synchronization operation. The NE LNP database may have been re-synchronized as a result of a download from the LSMS as a result of a procedure in Managing Bulk Load from the LSMS.
-
LSMS GUI Messages lists in alphabetical order the messages that can appear when using the LSMS GUI functions described in this manual.
-
Enabling RTDBLSMS Audit on ELAP shows how to enable an LSMS audit when it has been disabled. By default, an ELAP allows an audit from the LSMS, but the user may have disabled this ability in order to debug a problem. An LSMS audit, as described in Auditing and Reconciling Network Elements from the LSMS cannot be performed unless the ELAP has this setting enabled.
-
LNP Database Synchronization Files describes the files that are recorded when the various types of LNP database synchronization are performed.
-
Synchronization Performance Estimates provides estimates of the transaction rates for the various LNP database synchronization operations. Using these estimates can help decide which type of operation to use, as described in Choosing a Database Maintenance Procedure.
Related Publications
For information about additional publications related to this document, refer to the Oracle Help Center site. See Locate Product Documentation on the Oracle Help Center Site for more information on related product publications.