1.2 Terminology

Table 1-1 Terminology

Term	Definition
Site	Applicable for various applications, a site is type of place. A place is configured object that allows servers to be associated with a physical location. A site place allows servers to be associated with a physical site. For example, sites may be configured for Atlanta, Charlotte, and Chicago. Every server is associated with exactly one site when the server is configured. For the Policy and Charging DRA application, when configuring a site, only put DA‑MPs and SBR MP servers in the site. Do not add NOAM, SOAM, or IPFE MPs to a site.
Place Association	Applicable for various applications, a Place Association is a configured object that allows places to be grouped together. A place can be a member of more than one place association. The Policy and Charging DRA application defines two place association types: policy binding region and Policy and Charging mated sites.
Policy and Charging SBR Server Group Redundancy	The Policy and Charging application use SBR server groups to store the application data. The SBR server groups support both two and three site redundancies. The server group function name is Policy and Charging SBR.
Server Group Primary Site	A server group primary site is a term used to represent the principle location within a SOAM or SBR server group. SOAM and SBR server groups are intended to span several sites (places). For the Policy and Charging DRA application, these sites (places) are all configured within a single Policy and Charging Mated Sites place association. For the Diameter custom application, these sites (places) are configured in Applications Region place association. The primary site may be in a different site (place) for each configured SOAM or SBR server group. A primary site is described as the location in which the active and standby servers reside. However, there cannot be any preferred spare servers within this location. All SOAM and SBR server groups have a primary site.
Server Group Secondary Site	A server group secondary site is a term used to represent location in addition to the Primary Site within a SOAM or SBR Server Group. SOAM and SBR server groups are intended to span several sites (places). For the Policy and Charging DRA application, these sites (places) are all configured within a single Policy and Charging Mated Sites place association. For the Diameter custom application, these sites (places) are configured in Applications Region place association. The secondary site may be in a different site (places) for each configured SOAM or SBR server group. A secondary site is described as the location in which only preferred spare servers reside. The active and standby servers cannot reside within this location. If two site redundancy is wanted, a secondary site is required for all SOAM and SBR server groups.
Session Binding Repository Server Group Redundancy	The DCA application may use SBR server groups to store application session data. The SBR server groups support both two and three site redundancies. The server group function name is Session and Binding Repository.
Two Site Redundancy	Two site redundancy is a data durability configuration in which Policy and Charging data is unaffected by the loss of one site in a Policy and Charging Mated Sites Place Association containing two sites. Two site redundancy is a feature provided by server group configuration. This feature provides geographic redundancy. Some server groups can be configured with servers located in two geographically separate sites (locations). This feature ensures there is always a functioning active server in a server group even if all the servers in a single site fail.