A binding is a relationship stored in the SBR-B between various subscriber data session identities, such as MSIDN/IP Address(es)/IMSI and the assigned PCRF. A session is a relationship stored in the Session SBR that associate additional sessions with a binding.
Binding-dependent sessions are created by Rx, Gx-Prime, or S9 version of Rx AAR messages.
Figure 1 shows an overview of binding-dependent session initiation requests using IPv4 or IPv6 as correlation keys .
Binding Dependent Session Initiation Request Processing Overview
The following logic is used to locate an IP address Binding (used by binding-dependent interfaces):
- If PCRF Pooling is enabled, search the IpXAlternateKey table for a match, and if found, establish the alternate key. If the IP address is not found in the IpXAlternateKey table, search the IpXAlternateKeyV2 table for a match. If a match is found, the result is a binding fount to PCRF X, which completes the process. If a match is not found, the result is vinding not found, which competes the process.
- Binding-dependent session initiation requests using MSISDN as correlation key.
- Both MSISDN-Only and MSISDN+APN binding tables are audited.
- Both old and new IPv4 and IPv6 binding tables are audited.
Note: It is possible to determine the progress of data migration from the IMSI Only table by looking at the "Records Visited" statistic in the audit reports contained in event 22716. The records visited number shows how many IMSI Only records still remain. If no event 22716 occurs for the ImsiAnchorKey table, the migration is complete.
Binding-dependent Session Initiation Request Processing Rules and RequirementsBinding-capable request processing uses the binding key priority table to determine which keys present in the message should have alternate keys created in the binding database. Binding-dependent processing uses the binding key priority configuration to determine which keys to use and in what priority order when attempting binding correlation. See
Related Topics