In this section:

The PCE architecture supports two Signaling Transfer Points (STPs, see the following figure) for the public and private networks. The two networks are connected by the PCE process that provides the transfer and conversion of messages between them.

Note

The Enhanced PCE supports three STPs in a similar architecture.

PCE Architecture

Mated Pair Deployments

For PCE deployments of the Signaling System (see Figure PCE Architecture) in a STP mated-pair configuration, it is highly recommended that 100/Mbits/s to 1Gbits/s bandwidth is reserved for PCE traffic.

Note

STP mated-pairs are typically located in different geographic locations for redundancy and the dedicated bandwidth ensures delivery of time sensitive SS7 traffic over SCTP without competing with other IP traffic.


Filtering

If required to manage a large number of records for Public Nodes, Private Nodes, Public Gateways, and Trunk Mappings (refer to PCE Maximums), use the PCE Web UI filter capabilities. The Web UI filters large number of these database records based on criteria you define in the Web UI, takes a snapshot of these records, and displays the filtered information in the Web UI for your use.

There are two ways to access a filter table – as an SS7ADMIN user with read/write access or as a monitor user with read-only access.

Note

A maximum of 16 concurrent users can access a filtered table, but only one of the 16 can have the read/write access.  Non-monitor users have the ability to enter the table in read-only access if the read/write access is already in use.

A total of 96 sessions are allowed to access the filtered tables in PCE.

Beyond the 96 user maximum on the PCE, there is always a minimum of one read/write or read-only session guaranteed per table.

Multiple tabs do not equal multiple sessions; however, opening different browsers does create multiple sessions.

Monitor users and users selecting read-only access can only filter up to a maximum of 2,000 records. If the output of the criteria exceeds this maximum, an error will be returned requesting a fine-tune of the criteria for a more restricted output.

If you access a filtered table as a read/write user, the Web UI locks the given table until your task is complete. Clearing the lock may take place in the following three ways:

  • after you back out of the filtered table, the Web UI automatically unlocks this table

  • if more than an hour has passed since any activity has occurred

  • another read/write user unlocks the filtered table in the Web UI

If another read/write user wants to unlock the table, the Web UI displays a caution message that the respective filtered table is locked by <username of current read/write user> and unlocking this table forces the release of the table. If the new user only wants to view the PCE, there is an option to continue with Read Only access as a monitor user. Otherwise, the user can force an unlock in order to edit the table. See the following figure.

Example of a locked warning message


Filtered information is usually associated with other records or lists from different tables. The Soft Link feature helps link related filtered records and lists across multiple database tables for PCE application. The Soft Link (displayed as an arrow on the Web UI, see the following figure) is created between a record or list according to the creation and provisioning hierarchy of the PCE application. As a result, Soft Links have a one-way relationship between database records and lists.

Note

While PCE does have a hierarchy, it is not as enforced as GTT or GWST.

PCE Soft Link Example

Note

Soft Links do not appear in the Web UI if there is no record or table to link to the attribute.

In the PCE Live and Workspace DB configuration screens, any filtered objects with related records act as soft links (see the following figure).

Trunk Mappings Filtering Example

 
For PCE, links to records or lists are retrieved using the name based attributes from the following:

Note

The selected attribute depends on the originating record.

  • Private Node Name
  • Public Node Name
  • TCAP Private Node Name
  • Public Gateway Name
  • TCAP Public Gateway Name

If the table owning the linked record or list of records is locked, a warning message appears requesting the user decide to continue with read only access or to unlock the table, forcing the release of the table from the current user who is viewing or editing a record in the table.

Note

After clicking a filtered Soft Link selection, the back button cannot be used to return to the originating record. To get back to the originating record, a new filter must be applied on the given table. This filter application can trigger the lock warning prompt if that table is in use by another user.


  • No labels