In this section:
The Integrated Monitoring Feed (IMF) is a licensed feature that is supported on the DSC Platform.
Overview
The IMF provides interested MSUs or Diameter messages as they enter or exit the DSC Platform in sequential order to an external monitoring application (or a third party probe) over IP. Each MSU or Diameter message is sent using a connection specific interface that includes generic information such as time stamp, link/user ID, direction, NA or Node, SS7 Variant (where applicable), and media type.
The following is a list of all the various media types:
- LSL
- ANNEXA
- M2PA
- M2UA
- ATM
- M3UA
- SUA
- CICUA
- SIP
- IPSP
- M3UA_MG
- DIAMETER
- M3UA_SG
- M3UA_SERVER
The external monitoring application provides network analysis and external data representation (XDR) for the DSC Platform.
The IMF applies to incoming and outgoing Adjacent Diameter Nodes (ADNs) and SS7 link-based and standard IP traffic (SUA, M3UA, and CIC UA).
The IMF solution spans the Routing VMs (Routing CPUs) within a system over all NAs and Nodes.
Up to five external monitoring application interfaces and IP transport are configurable on a per Routing VM-basis (Routing CPU-basis). TCP/IP connectivity is supported between the IMF and external IP monitoring application using a dedicated port. For information about the DSC Platform networking configuration, see the Installation Guides.
This section provides the supported protocol definitions.
IMF Default Protocol
The IMF Default Protocol is a fixed format protocol managed by IMF. The traffic processes (MTP3, SG, and DSC) are designed with an access or function to transfer the messages and/or data packets to the IMF process.
Field Definitions
The definitions of the protocol parameter enumerators are listed and described in the following tables.
MSU Direction Definitions
| Enumerator | Description |
|---|---|
| 0 | Unknown |
| 1 | Incoming |
| 2 | Outgoing |
SS7 Variant Definitions
| Enumerator | Description |
|---|---|
| 0 | Unknown/Not Applicable |
| 1 | ANSI |
| 2 | ITU |
| 3 | CHINA |
| 4 | JAPAN |
Link Media Definitions
| Enumerator | Link Media | Description | Application |
|---|---|---|---|
| 0 | Unknown | Unknown link media | DRE |
| 3 | M2PA | M2PA Link | DRE |
| 4 | M2UA | M2UA Link | DRE |
| 6 | M3UA | M3UA ASP Association | SG |
| 7 | SUA | SUA ASP Association | SG |
| 8 | CIC UA | CIC UA ASP Connection | SG |
| 10 | IPSP | IPSP Link | DRE |
| 11 | M3UA MG | Media Gateway Link | DRE |
| 12 | Diameter | DSC ADN Connection | DSC |
| 13 | M3UA SG | M3UA SG Link | DRE |
| 14 | M3UA Server | M3UA Server Link | DRE |
Link Status L3 State Definitions
| Enumerator | Description |
|---|---|
| 0 | Unknown |
| 1 | In Service |
| 2 | Out of Service |
Version Message Format
The version message (see the following table) is used to assist in system upgrades and external interface conversion.
Version Message Format
| Octet | Field | Description |
|---|---|---|
| 0 | Message Header | The message header. For more information, see Using a Message Header to Delimit Message Boundaries. |
| 1 | ||
| 2 | ||
| 3 | ||
| 4 | Message Type | The message type. 0xFE reserved for version. |
| 5 | Version | Most Significant Bit (MSB) - Least Significant Bit (LSB) encoding. Release 9.0.0 is coded as 1. Release 9.1.0 is coded as 2. Release 14.0.0 is coded as 3. Release 17.0.0 is coded as 4. NOTE: For version 4, the SG Traffic Message octet 15 and 17 for Link Media Types M3UA and SUA are altered, see Traffic Message Format. |
| 6 | ||
| 7 | ||
| 8 | ||
| 9 | Virtual Slot | Virtual Slot number of IMF. MSB - LSB Encoding. |
| 10 | ||
| 11 | ||
| 12 |
Traffic Message Format
The traffic message (see the following figure and table) has a header length of 22 bytes and is used to send each MSU/Data to the external monitoring applications.
Traffic Message Format
Traffic Message Format
| Octet | Field | Description |
|---|---|---|
| 0 | Message Header | The message header. For more information, see Using a Message Header to Delimit Message Boundaries. |
| 1 | ||
| 2 | ||
| 3 | ||
| 4 | Message Type | The message type. 0xFD reserved for traffic. |
| 5 | Time Stamp (seconds) | UTC seconds. |
| 6 | ||
| 7 | ||
| 8 | ||
| 9 | Time Stamp (milliseconds) | UTC milliseconds. |
| 10 | ||
| 11 | Sequence Number | Unique sequence number on a per connection basis. |
| 12 | ||
| 13 | ||
| 14 | ||
| 15 | NA/DSC Node ID/Slot | Network Appearance for DRE, DSC Node ID (1-99), or ASP Association Slot. NOTE: Protocol version 4 changes the SG Traffic Message format from NA to ASP Association Slot. The MTP3 and DSC Traffic Message values are unchanged. |
| 16 | SS7 Variant | SS7 Variant. For more information, see SS7 Variant Definitions. NOTE: Set to NOT APPLICABLE for DSC traffic. |
| 17 | Link/ADN Connection/ASP ID | Unique ID on a per NA, DSC Node, or ASP basis. NOTE: Protocol version 4 changes the SG Traffic Message format from Link ID to ASP ID. The MTP3 and DSC Traffic Message values are unchanged. |
| 18 | ||
| 19 | ||
| 20 | ||
| 21 | MSU Direction | MSU Direction. For more information, see MSU Direction Definitions. |
| 22 | Link Media | Link Media. For more information, see Link Media Definitions. |
| 23 | Application Instance ID | For SS7 and SG IP traffic, coded as 0x00. For DSC traffic, coded as the DSC Instance ID. |
| 24 | Reserved | Coded as 0x00. |
| 25 | MSU/Data Length | For SS7 traffic, MSU length starting at SIO. For SG IP and DSC traffic, payload length of the messages. |
| 26 | ||
| 27 | MSU/Data | Actual MSU/Data as per length. |
| .... |
Link Status Message Format
MTP3 provides link status to the IMF external monitoring application thorough a new link status message as of Release 9.1.0 (Version 2). These messages are provided for M2UA and M2PA and reflect the Level 3 link status (see Table Link Status L3 State Definitions).
The IMF link status message is only sent on a change in L3 status for local links on the given slot. The only exception to this is on a link switchover where an L3 state message is sent on accepting the new link. For a newly created link in an IMF supported linkset a message is sent regarding the L3 status when this link becomes active and any changes thereafter.
The link status message is a fixed length of 20 octet (see the following figure and table).
Link Status Message Format
Link Status Message Format
| Octet | Field | Comment |
|---|---|---|
| 0 | Message Header | The message header. For more information, see Using a Message Header to Delimit Message Boundaries. |
| 1 | ||
| 2 | ||
| 3 | ||
| 4 | Message Type | The message type. 0xFC reserved for link status. |
| 5 | Time stamp (seconds) | UTC seconds |
| 6 | ||
| 7 | ||
| 8 | ||
| 9 | Time stamp (milliseconds) | UTC milliseconds |
| 10 | ||
| 11 | Sequence Number | Unique sequence number on a per connection basis. |
| 12 | ||
| 13 | ||
| 14 | ||
| 15 | NA | Network Appearance (1-8) |
| 16 | SS7 Variant | See SS7 Variant Definitions. |
| 17 | Link/User ID | Unique ID on a per NA basis. |
| 18 | ||
| 19 | ||
| 20 | ||
| 21 | Link L3 State | See Link Status L3 State Definitions. |
| 22 | Link Media | See Link Media Definitions. |
| 23 | Out of Service Cause | If Link State is not set to Out of Service, coded as 0x00. |
Overview
Content Tools