3.3 Service Module Card Provisioning
One of the core functions of the ELAP is to provision the Service Module cards with database updates. The ELAP provides Real Time database (RTDB) loading and provisioning functions for the EAGLE Service Module cards using the main DSM network between the MPS system and the EAGLE Service Module cards; the backup DSM network is used, if necessary. Real-time updates are sent to the EAGLE Service Module cards in parallel using UDT technology.
The VSCCP application, running on the Service Module cards, conducts all database communications between the Active ELAP and each Service Module card.
The LNP feature auto-inhibits any Service Module card that does not meet the minimum hardware requirements based upon feature quantity capacities and the LNP ELAP Configuration feature status. See Hardware, System, and Feature Requirements for more information on minimum requirements.
3.3.1 Incremental Loading
Incremental loading occurs when a Service Module card has missed some updates, but does not need a complete reload.
The ELAP can broadcast a stream of current updates to all Service Module cards at a rate of 100 updates per second. When the ELAP detects that a Service Module card is back-level from the current provisioning stream, the ELAP attempts to start a new stream at that level.
Note:
Incremental loading and normal provisioning are done in parallel. The Service Module card provisioning task supports up to five incremental loading streams in addition to the normal provisioning stream.Incremental reload streams are terminated when the database level contained in that stream matches that of another stream. This is expected to happen most often when the incremental stream “catches up to” the current provisioning stream. Service Module cards accept any stream with the “next” sequential database level for that card.
3.3.2 Service Module Card Reload
Service Module cards might require a complete database reload in the event of reboot or loss of connectivity for a significant amount of time. The ELAP provides a mechanism to quickly load a number of Service Module cards with the current database. The database on the ELAP is large and may be updated constantly. The database sent to the Service Module card or cards is likely to be missing some updates, making it corrupt as well as back level. The upload process is divided in to two stages, one to sequentially send the raw database records and another to send all of the updates missed since the beginning of the first stage. The Service Module card reload stream uses a separate UDT channel from the provisioning and incremental update streams.