Overwrite

The file specification replaces the existing one.

Rename

Skip

The file specification is not imported.

On Current Definition Only

Apply the selection of Overwrite, Rename, or Skip, only to the current specification.

On All Upcoming Definitions

Apply to all future imported specifications.

Name

The command name. For example: Credit-Control-Request.

Code

The unique numeric command code. For example: 272. For further information, see Show Base Commands.

Application ID

The numeric representation of the Diameter Application that this command belongs to. For example: 4 - Diameter Credit-Control.

Show Base Commands

Select this check box to view predefined commands, their numeric code, and Application ID. These are the commands specified in Diameter Base Protocol (RFC 6733).

Command Name

Enter a unique command name.

When you save the configuration, a UDR type with the specified name will be generated.

Command Code

Enter a numeric command code. Each command that belongs to the same Diameter Application must have a unique code.

Application ID

The numeric representation of the Diameter Application that the command belongs to.

Flags

Select the Request check box to mark the command as a request message (r-bit is set in Diameter message header); clear the Request check box to mark the command as an answer message.

Select Proxiable to enable the command to support proxy, relay, or redirection (p-bit is set in Diameter message header). For more information about the Proxiable flag, see the Diameter Base Protocol (RFC 6733). This flag is set by default when a new command is added.

Select Error to mark that the message contains a protocol error (e-bit is set in Diameter message header), so that the message will not conform to the ABNF described for this command. This flag is typically used for test purposes. If you want to send an error message answer from APL, it is recommended that you use the UDR Diameter.Base.Error_Answer_Message.

Auto-Populate

Category

There are three different AVP categories:

• A Fixed AVP must be included in its predefined space in the command.

• A Required AVP must be included, but may appear anywhere in the message.

• An Optional AVP can appear anywhere in the message.

AVP

Enter or modify an AVP name.

Min

Enter the lowest number of AVPs that the command should contain.

Max

Enter the highest number of AVPs that the command should contain.

Auto-Populate

Click this button to enter missing table entries in all the user defined AVPs of a command in the table.

Name

The AVP name

Code

The numeric code that represents the AVP. This number is unique and fixed for every AVP. For further information, see the AVP specifications. For example: RFCs.

Type

The AVP data format as specified in the Diameter Base Protocol (RFC 6733). UDR types are generated for the Diameter application profile based on the AVP configuration. The AVP data formats are mapped to the UDR data types as follows:

Address - ipaddress

DiameterIdentity - string

Enumerated - int

Grouped - list<type>

Float32 - float

Float64 - double

IPFilterRule - IPFilterRuleUDR(Diameter)

OctetString - bytearray

Signed32 - int

Signed64 - long

Time - date

Unsigned32 - int

Unsigned64 - long

UTF8String - string

Vendor

The numeric Vendor ID of the AVP. The vendor ID of all the IETF standard Diameter applications is 0 (zero).

Show Base AVPs

To display all predefined AVP types, check Show Base AVPs. These are the AVPs specified in  Diameter Base Protocol (RFC 6733).

AVP Name

The name of the AVP.

AVP Code

The numeric id of the AVP.

Vendor ID

The number that represents the vendor. The default value is 0 (zero).

AVP Type

Mandatory ('M') Bit

The M-bit allows the sender to indicate to the receiver whether or not understanding the semantics of an AVP and its content is mandatory. If the M-bit is set by the sender and the receiver does not understand the AVP or the values carried within that AVP, then a failure is generated. For further information about the M-bit, see the Diameter Base Protocol (RFC 6733).

The following applies for incoming and outgoing messages that contains the configured AVP:

MUST:The M-bit is set to 1 in outgoing messages and must be set to 1 in incoming messages.

MAY:The M-bit is set to 0 or 1 (configurable in the Advanced tab) in outgoing messages and may be set to 0 or 1 in incoming messages.

SHOULD:The M-bit is set to 0 in outgoing messages and may be set to 0 or 1 in incoming messages.

MUST NOT:The M-bit is set to 0 in outgoing messages and must be set to 0 in incoming messages.

You can change the value of the M-bit from APL if Mandatory ('M') Bit is set to MAY or SHOULD.

Protection ('P') Bit

 The P-bit bit is reserved for future usage of end-to-end security.

Enumeration/Group Properties

This table is accessible for editing only when AVP Type is configured as Enumerated or as Grouped. This table enables you to add, edit, or remove AVPs or enumeration values. For further information about the tables columns and entries, see the section above, To Add a Diameter Command Specification.

Auto-Populate

Application ID

Numeric codes of the supported applications.

Authentication

Select and check to flag an application with Authentication.

Accounting

Select and check to flag an application with Accounting.

Vendor ID

Enter the numeric code of the vendor

Auth App ID

Enter the vendor specific authentication application ID.

Acct App ID

Enter the vendor specific accounting application ID.