Erlang -- Introduction

User's Guide
Reference Manual
Release Notes
PDF
Top

Diameter
User's Guide
Version 1.1

Expand All
Contract All

Chapters

- Introduction
  - Top of chapter
- Using the stack
  - Top of chapter
- Examples
  - Top of chapter
- Standards Compliance
  - Top of chapter
  - RFC 3588
  - RFC 3539

# 1 Introduction

The diameter application is an implementation of the Diameter protocol as defined by RFC 3588. It supports arbitrary Diameter applications by way of a dictionary interface that allows messages and AVP's to be defined and input into diameter as configuration. It has support for all roles defined in the RFC: client, server and agent. This chapter provides a short overview of the application.

A Diameter peer is implemented by configuring a service and one or more transports using the interface module diameter. The service configuration defines the Diameter applications to be supported by the peer and, typically, the capabilities that it should send to remote peers at capabilities exchange upon the establishment of transport connections. A transport is configured on a service and provides protocol-specific send/receive functionality by way of a transport interface defined by diameter and implemented by a transport module. The diameter application provides two transport modules: diameter_tcp and diameter_sctp for transport over TCP (using gen_tcp) and SCTP (using gen_sctp) respectively. Other transports can be provided by any module that implements diameter's transport interface.

While a service typically implements a single Diameter peer (as identified by an Origin-Host AVP), transports can themselves be associated with capabilities AVP's so that a single service be used to implement more than one Diameter peer.

Each Diameter application defined on a service is configured with a callback module that implements the application interface through which diameter communicates the connectivity of remote peers, requests peer selection for outgoing requests, and communicates the reception of incoming Diameter request and answer messages. An application using diameter implements these application callback modules to provide the functionality of the Diameter peer(s) it implements.

Each Diameter application is also configured with one or more dictionary modules that provide encode/decode functionality for outgoing/incoming Diameter messages. A module is generated from a specification file using the diameterc utility. Dictionaries for the RFC 3588 Diameter Common Messages, Base Accounting and Relay applications are provided by the diameter application.