5.2 NOAM and SOAM Configuration

Configuration data is divided into two categories depending on the scope of the data:

• Network-wide data is configured at the NOAM and is called A-scope data.
• Per-site data is configured at the SOAM for a given site and is called B-scope data.

In general, topology data like creation of sites, assignment of servers to sites, creation of server groups, and so on is A-scope data. DSR data configuration is generally site-scoped, or B-scope data.

Some Policy and Charging Application data must be configured at the A-scope level and some data must be configured at the B-scope level.

Policy related data configured at the NOAM include:

• Assignment of Servers to Site Places
• Assignment of Servers to SBR Server Groups
• Assignment of SBR Server Groups to Session and/or Binding Resource Domains
• Assignment of DSR Multi-active Cluster Server Groups to PCA Resource Domains
• Assignment of Site Places to PCA Mated Sites Place Associations
• Assignment of Site Places to PCA Binding Region Place Associations

PCA-specific data configured at the NOAM include:

• Alarm Thresholds for:
  • PCA Application Ingress Message Rate
  • Session Database Capacity
  • Policy Binding Database Capacity
• Policy DRA and Online Charging DRA function disabling/enabling
• Default Audit options
• OCS/Realm Session State
• Access Point Names (APN)
• Maximum Session Inactivity Time per APN
• PCRF Pools and PCRF Sub-Pool Selection Rules
• SBR Databases
• SBR Database Resizing Plans
• SBR Data Migration Plans

PCA-specific data configured at the SOAM include:

• PCRFs adjacent to the site
• Binding Key Priority for the site
• Topology Hiding configuration for the site
• OCSs and CTFs for OC-DRA
• Error response configuration for the site
• Congestion handling options
• Suspect Binding Removal Rules

For more information, see PCA Capacity Constraints.