1. Full Address Based Resolution User Guide
  2. Full Address Based Resolution
  3. Transaction Metadata Recording for Integrated DIH (IDIH)

2.5 Transaction Metadata Recording for Integrated DIH (IDIH)

Integrated Diameter Intelligence Hub (IDIH) can be used to capture detailed information about selected Diameter transactions, and transmit this information to DIH for further analysis.

The Diameter Routing Function and invoked DSR applications record detailed information about each Diameter transaction - called transaction metadata. Each metadata record describes an important event in the lifetime of a Diameter transaction. Metadata appears in the Trace Transaction Record (TTR) in the order that the metadata-generating events actually occurred. Together, all of the metadata records combine to document the processing performed on the entire transaction, and can later be used to provide diagnostic information when performing troubleshooting. Metadata is recorded to a TTR for each transaction so that, even if the transaction is selected to be sent to DIH at an Answer Troubleshooting Trigger Point (TTP-IA or TTP-EA), the metadata for all of the messages in the transaction is present.

The functions of IDIH are described in the Integrated DIH User's Guide and Help.

FABR records the application-specific metadata events described in Table 2-5.

Table 2-5 FABR Metadata-Generating Events

Event Type Scope Instance Data When Recorded
Address Resolution Match found

Address Resolution

Match

 App Data
  • Routing Entity Type (such as IMSI)
  • Routing Entity AVP (such as Public-Identity)
  • Routing Entity Address (such as 311480123456789)
 After FABR searches and finds a valid Routing Entity address in an ingress Request message using a prioritized set of AVPs associated with the highest priority Routing Entity Type assigned to the Address Resolution order pair (Diameter Application ID, Command Code).
DP Query Event Sent to DP for processing DP Query Sent App Data
  • Routing Entity Data Format (such as IMSI)
  • Routing Entity Address (such as 123456789012345)
  • Destination Type (such as IMS-HSS)
When FABR sends a DP query event to the DP for Destination address resolution.
DP Response Event Received from DP DP Response Received App Data
  • DP IP Address Type (such as IPv4)
  • DP IP Address (such as 10.240.55.25)
  • Result Code String (such as Blacklisted)
  • Destination Realm (such as xyz.com)
  • Destination FQDN (such as hss1.hss.xyz.com)
 When FABR receives a response to a previous DP query.
Routing Exception Routing Exception App Data
  • Routing Exception Type (such as DP Congestion)
  • Routing Exception Action (such as Abandon Request)
 After any Routing Exception is encountered.
DP Query Failure DP Query Failure App Data
  • DP IP Address Type (such as IPv4)
  • DP IP Address (such as 10.240.55.25)
 After any DP Query failure other than a response timeout is encountered.
DP Response Timed out DP Response Timeout App Data
  • DP IP Address Type (such as IPv4)
  • DP IP Address (such as 10.240.55.25)
 When FABR times out waiting to receive a response from the DP to a previous Destination address resolution query.