2.5 Metadata Recording for Integrated DIH (IDIH)

Integrated DIH (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.

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

Table 2-5 RBAR 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 User Name) Routing Entity Address (such as 123456789012345)	After RBAR 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).
Routing Entity address resolved to a Destination address for request message routing	Destination Resolution	App Data	Destination Routing Table Format (such as AET) Destination Realm (such as xyz.com) Destination FQDN (such as hss1.hss.xyz.com)	When a valid Routing Entity address extracted from an Ingress Request message matches an AET or DRT entry for request message routing.
Routing Exception	Routing Exception	App Data	Routing Exception Type (such as Unknown Command Code) Routing Exception Action (such as Abandon Request)	After any Routing Exception is encountered.