In this version:
- Enhancing the capability (e.g. Support multiple vendors per application)
- New export module (to a generic XML Dictionary)
- Some bugs fixed & GUI improvements
- Users need to input data by themselves as only DIAMETER base and 3GPP Rx are available (Please using version 0.9 for more 3GPP-related data)
OpenDPS is packaged with Server2Go and available for download at SourceForge.
Get it, spend a minute in the README for further information !
OpenDPS is packaged with Server2Go that can run easilly without any installation.
- DIAMETER applications supported: DIAMETER base protocol (RFC 3588), several common 3GPP DIAMETER applications (e.g. S6a/S6d, S9, Rx, Gx, Gxx)
- Exported functions: Two examples (export to Seagull and Wireshark protocol dictionaries)
OpenDPS is available for download from the SourceForge. Get it, spend a minute in the README file and try !
 Server2Go: Portable Web Server (Apache + PHP + MySQL)
 Seagull: An Open Source Multi-protocol traffic generator
 Wireshark: The world’s foremost network protocol analyzer
OpenDPS is a free, open source (GPL) web-based DIAMETER provisioning system. Provisioning, in this context, is the process of equipping related tools and products with necessary information to support DIAMETER protocol and required DIAMETER applications. The information, which describes protocol such as data types and message structures (protocol dictionary), is often extracted from the relevant DIAMETER standards (RFC) and technical specifications (TS).
In OpenDPS, several open source solutions have been selected to develop the system: MySQL database, Apache web server and PHP programming language. The architecture is described in Figure 1.
Figure 1: OpenDPS Architecture
- Scalable & Extensible: Allowing new applications definition, new messages within the given application, new export functions development etc.
- Free of use: Users (e.g. engineers, academicians) can use this tool to assist their researches and works.
Figure 2: OpenDPS GUI
OpenDPS is free. However, if you just want to say “thank you”, you should contribute your results to the project (e.g. new specific dictionary files, new export modules) as other users can take benefit from your works.
You can download the current results from SourceForge.
Please send any comments and bug reports to firstname.lastname@example.org
The DIAMETER protocol  has been specified by the Internet Engineering Task Force (IETF) since 1998 as a renovated version of previous Authentication Authorization and Accounting (AAA) RADIUS protocols to offer more flexibility, reliability, scalability and security. In the design, DIAMETER base protocol offers only basic functions and services. Standardization bodies and vendors (e.g. IETF, 3GPP, ETSI) have extent the base protocol to create other specific applications (interfaces).
Figure 1: DIAMETER message structure
The structure of a DIAMETER message is depicted in Figure 1 including the message header and payload. In the header, the command code and flag fields are used to distinguish DIAMETER message from other ones. The Application Identifier (Application-ID) field is used to identify to which application the message belongs to and its values are defined and allocated by Internet Assigned Numbers Authority (IANA). The message payload encapsulates data in a sequence of Attribute Value Pairs (AVPs) field. Many DIAMETER commands and AVPs have already been defined and widely used. Nevertheless, standardization bodies and vendors can update them or define new ones, if necessary.
Figure 2: Emerging DIAMETER network (from Tekelec)
3GPP  has a lot of influence on the development of the DIAMETER protocol. Although IETF has specified DIAMETER base protocol and some applications, DIAMETER acceptance and deployment were still behind the ancestor RADIUS in a long time. Recognizing the value of DIAMETER versus RADIUS in mobile environments, 3GPP selected DIAMETER to be the main control protocol in IP Multimedia Subsystem (IMS) and NGN networks. The central role of DIAMETER protocol has continuously been confirmed when 3GPP introduced its new all-IP core network architecture Evolved Packet Core (EPC) and DIAMETER was the signaling protocol that every entity must support. The signaling planes of emerging mobile networks are now considered as DIAMETER networks . These networks communicate many service and network control components (e.g. policy server, billing system, gateway, mobility and session management, subscriber databases).
 IETF RFC 3588: Diameter Base Protocol, http://www.ietf.org
 The 3rd Generation Partnership Project (3GPP), http://www.3gpp.org
 The new Diameter network, Tekelec, 2011