1 Diameter Base Protocol

This chapter describes how Oracle Communications Billing and Revenue Management (BRM) Elastic Charging Engine (ECE) Diameter Gateway maps the diameter messages for Diameter Base Protocol defined in RFC-3588. For more information, see the Diameter Base protocol specification detail:

https://www.rfc-editor.org/info/rfc3588

Section Compliance

Table 1-1 lists the compliance information for Diameter Base protocol sections.

Table 1-1 Diameter Base Protocol Section Compliance

Section Number Section Status Notes

1

Introduction

Not applicable

-

1.1

Diameter Protocol

Not applicable

-

1.1.1

Description of the document set

Not applicable

-

1.2

Approach to extensibility

Not applicable

-

1.2.1

Defining new attribute-value pair (AVP) values

Not applicable

-

1.2.2

Creating new AVPs

Not applicable

-

1.2.3

Creating new authentication applications

Not applicable

-

1.2.4

Creating new accounting applications

Not applicable

-

1.2.5

Application authentication procedures

Not applicable

-

1.3

Terminology

Not applicable

-

2

Protocol overview

Not applicable

-

2.1

Transport

Supported

Supports Transmission Control Protocol (TCP) and Stream Control Transmission Protocol (SCTP).

2.1.1

Stream control transmission protocol guidelines

Supported

-

2.2

Securing diameter messages

Not supported

-

2.3

Diameter application compliance

Supported

-

2.4

Application identifiers

Supported

-

2.5

Connections vs Sessions

No requirement

-

2.6

Peer table

Supported

-

2.7

Realm-based routing table

Not applicable

-

2.8

Role of diameter agents

Not applicable

-

2.8.1

Relay agents

Not applicable

-

2.8.2

Proxy agents

Not applicable

-

2.8.3

Redirect agents

Not applicable

-

2.8.4

Translation agents

Not applicable

-

2.9

End-to-end security framework

Not supported

-

2.10

Diameter path authorization

Not supported

-

3

Diameter header

Supported

-

3.1

Command codes

Supported

-

3.2

Command code augmented backus–naur form (ABNF) specification

No requirement

-

3.3

Diameter command naming conventions

Supported

-

4

Diameter AVPs

Supported

-

4.1

AVP header

Supported

-

4.1.1

Optional header elements

Supported

-

4.2

Basic AVP

Supported

-

4.3

Derived AVP data formats

Supported

-

4.4

Grouped AVP values

Supported

-

4.4.1

Example AVP with a grouped data type

No requirement

-

4.5

Diameter base protocol AVPs

Supported

-

5

Diameter peers

No requirement

-

5.1

Peer connections

Supported

-

5.2

Diameter peer discovery

Not supported

Diameter Gateway does not support routing, proxy, or relay

5.3

Capabilities exchange

Supported

-

5.3.1

Capabilities-Exchange-Request

Supported

-

5.3.2

Capabilities-Exchange-Answer

Supported

-

5.3.3

Vendor-Id AVP

Supported

-

5.3.4

Firmware-Revision AVP

Supported

-

5.3.5

Host-IP-Address AVP

Not supported

-

5.3.6

Supported-Vendor-Id AVP

Supported

-

5.3.7

Product-Name AVP

Supported

-

5.4

Disconnecting peer connections

Partially supported

Diameter Gateway does not generate this message but only responds to it.

5.4.1

Disconnect-Peer-Request

Partially supported

Diameter Gateway does not generate this message but only responds to it.

5.4.2

Disconnect-Peer-Answer

Partially supported

Diameter Gateway does not generate this message but only responds to it.

5.4.3

Disconnect-Cause AVP

Partially supported

Diameter Gateway does not generate this message but only responds to it.

5.5

Transport failure detection

Supported

-

5.5.1

Device-Watchdog-Request

Supported

-

5.5.2

Device-Watchdog-Answer

Supported

-

5.5.3

Transport failure algorithm

Supported

-

5.5.4

Failover and failback procedures

Partially supported

-

5.6

Peer state machine

Supported

-

5.6.1

Incoming connections

Supported

-

5.6.2

Events

Supported

-

5.6.3

Actions

Supported

-

5.6.4

The election process

Supported

-

6

Diameter message processing

No requirement

-

6.1

Diameter request routing overview

No requirement

-

6.1.1

Originating a request

Supported

-

6.1.2

Sending a request

Supported

-

6.1.3

Receiving requests

Supported

-

6.1.4

Processing local requests

Not supported

-

6.1.5

Request forwarding

Not supported

-

6.1.6

Request routing

Not applicable

-

6.1.7

Redirecting requests

Not applicable

-

6.1.8

Relaying and proxying requests

Not applicable

-

6.2

Diameter answer processing

Supported

-

6.2.1

Processing received answers

Supported

-

6.2.2

Relaying and proxying answers

Not applicable

Configurable per Diameter Gateway instance

6.3

Origin-Host AVP

Supported

Configurable per Diameter Gateway instance

6.4

Origin-Realm AVP

Supported

-

6.5

Destination-Host AVP

Supported

-

6.6

Destination-Realm AVP

Supported

-

6.7

Routing AVPs

Not applicable

-

6.7.1

Route-Record AVP

Not applicable

-

6.7.2

Proxy-Info AVP

Not applicable

-

6.7.3

Proxy-Host AVP

Not applicable

-

6.7.4

Proxy-State AVP

Not applicable

-

6.8

Auth-Application-Id AVP

Supported

-

6.9

Acct-Application-Id AVP

Not applicable

-

6.10

Inband-Security-Id AVP

Supported

Supports only 0, where 0 specifies NO_INBAND_SECURITY

6.11

Vendor-Specific-Application-Id AVP

Supported

-

6.12

Redirect-Host AVP

Not applicable

-

6.13

Redirect-Host-Usage AVP

Not applicable

-

6.14

Redirect-Max-Cache-Time AVP

Not applicable

-

6.15

E2E-Sequence AVP

Not applicable

-

7

Error handling

Supported

-

7.1

Result-Code AVP

Supported

-

7.1.1

Informational

Supported

-

7.1.2

Success

Supported

-

7.1.3

Protocol errors

Supported

-

7.1.4

Transient Failures

Supported

-

7.1.5

Permanent Failures

Supported

-

7.2

Error bit

Supported

-

7.3

Error-Message AVP

Not supported

-

7.4

Error-Reporting-Host AVP

Not supported

-

7.5

Failed-AVP AVP

Supported

-

7.6

Experimental-Result AVP

Supported

-

7.7

Experimental-Result-Code AVP

Supported

-

8

Diameter user sessions

No requirement

-

8.1

Authorization session state machine

Supported

-

8.2

Accounting session state machine

Not applicable

-

8.3

Server-Initiated Re-Auth

Supported

-

8.3.1

Re-Auth-Request

Supported

-

8.3.2

Re-Auth-Answer

Supported

-

8.4

Session termination

Supported

-

8.4.1

Session-Termination-Request

Supported

-

8.4.2

Session-Termination-Answer

Supported

-

8.5

Aborting a session

Not supported

-

8.5.1

Abort-Session-Request

Not supported

-

8.5.2

Abort-Session-Answer

Not supported

-

8.6

Inferring session termination from Origin-State-Id

Not supported

-

8.7

Auth-Request-Type AVP

Not applicable

-

8.8

Session-Id AVP

Supported

-

8.9

Authorization-Lifetime AVP

Not applicable

-

8.10

Auth-Grace-Period AVP

Not applicable

-

8.11

Auth-Session-State AVP

Not applicable

-

8.12

Re-Auth-Request-Type AVP

Not applicable

-

8.13

Session-Timeout AVP

Not applicable

-

8.14

User-Name AVP

Not applicable

-

8.15

Termination-Cause AVP

Supported

-

8.16

Origin-State-Id AVP

Not supported

-

8.17

Session-Binding AVP

Not applicable

-

8.18

Session-Server-Failover AVP

Not applicable

-

8.19

Multi-Round-Time-Out AVP

Not applicable

-

8.20

Class AVP

Not applicable

-

8.21

Event-Timestamp AVP

Supported

-

9

Accounting

Not applicable

-

9.1

Server directed model

Not applicable

-

9.2

Protocol messages

Not applicable

-

9.3

Application document requirements

Not applicable

-

9.4

Fault resilience

Not applicable

-

9.5

Accounting records

Not applicable

-

9.6

Correlation of accounting records

Not applicable

-

9.7

Accounting Command-Codes

Not applicable

-

9.7.1

Accounting-Request

Not applicable

-

9.7.2

Accounting-Answer

Not applicable

-

9.8

Accounting AVPs

Not applicable

-

9.8.1

Accounting-Record-Type AVP

Not applicable

-

9.8.2

Acct-Interim-Interval AVP

Not applicable

-

9.8.3

Accounting-Record-Number AVP

Not applicable

-

9.8.4

Acct-Session-Id AVP

Not applicable

-

9.8.5

Acct-Multi-Session-Id AVP

Not applicable

-

9.8.6

Accounting-Sub-Session-Id AVP

Not applicable

-

9.8.7

Accounting-Realtime-Required AVP

Not applicable

-

10

AVP occurrence table

No requirement

-

10.1

Base protocol command AVP Table

No requirement

-

10.2

Accounting AVP Table

No requirement

-

11

IANA Considerations

No requirement

-

11.1

AVP header

No requirement

-

11.1.1

AVP code

No requirement

-

11.1.2

AVP flags

No requirement

-

11.2

Diameter header

No requirement

-

11.2.1

Command codes

No requirement

-

11.2.2

Command Flags

No requirement

-

11.3

Application identifiers

No requirement

-

11.4

AVP Values

No requirement

-

11.4.1

Result-Code AVP Values

No requirement

-

11.4.2

Accounting-Record-Type AVP Values

No requirement

-

11.4.3

Termination-Cause AVP Values

No requirement

-

11.4.4

Redirect-Host-Usage AVP Values

No requirement

-

11.4.5

Session-Server-Failover AVP Values

No requirement

-

11.4.6

Session-Binding AVP Values

No requirement

-

11.4.7

Disconnect-Cause AVP Values

No requirement

-

11.4.8

Auth-Request-Type AVP Values

No requirement

-

11.4.9

Auth-Session-State AVP Values

No requirement

-

11.4.10

Re-Auth-Request-Type AVP Values

No requirement

-

11.4.11

Accounting-Realtime-Required AVP Values

No requirement

-

11.5

Diameter TCP/SCTP port numbers

No requirement

-

11.6

Naming authority pointer (NAPTR) Service Fields

No requirement

-

12

Diameter Protocol Related Configurable Parameters

Supported

-

13

Security considerations

Not supported

-

13.1

IPsec usage

Not supported

-

13.2

TLS usage

Not supported

-

13.3

Peer-to-Peer Considerations

Not supported

-

14

References

No requirement

-

14.1

Normative References

No requirement

-

14.2

Informative References

No requirement

-

15

Acknowledgements

No requirement

-

Appendix A

Diameter service template

No requirement

-

Appendix B

NAPTR example

No requirement

-

Appendix C

Duplicate detection

Supported

-