| Diameter Signaling Router Policy and Charging Application Release 8.2 E89000 |
|
 Previous |
 Next |
On receipt of a Gy/Ro Diameter Credit Control Application Request message, OC-DRA performs validation checks on the contents of the message before it attempts to route the message. Validation is limited to header information and routable Attribute Value Pairs (AVPs) that are used by OC-DRA for making processing decisions for routing
OC-DRA validates the Application ID and Command Code in the Diameter Request message for consistency. OC-DRA supports the Gy/Ro DCCA messages. If OC-DRA receives a Diameter Request message with a Command Code that is not supported, PCA will abandon message processing and send an Answer message with Result-Code set to DIAMETER_COMMAND_UNSUPPORTED (3001) and Error-Message AVP to the downstream peer that initiated the Diameter transaction.
OC-DRA also makes Diameter Request message processing decision based on the small subset of AVPs for online charging. Those Diameter AVPs that are used specifically by OC-DRA for making routing decisions and maintaining session state. These AVPs are shown in Table 5-3 and marked M, O, OM, or - to indicate which ones are mandatory, optional, optional-mandatory, or not used for each of the supported Gy/Ro Diameter Credit Control Application Request messages.
Note:
AVPs marked as OM are optional, but are mandatory if the optional Grouped AVP in which they are a member is present in the Diameter message.Table 5-3 Diameter AVPs used by OC-DRA for Request Message Processing
| AVP Name | AVP Code | Used In | Value Type | Description | |
|---|---|---|---|---|---|
| CCR | RAR | ||||
| Session-Id | 263 | M | M | UTF8String | Contains the session identifier. |
| Origin-Host | 264 | M | M | DiamIdent | Contains the end point that originated the Diameter message. |
| Origin-Realm | 296 | M | M | DiamIdent | Contains the realm of the originator of the Diameter message. |
| Destination-Host | 293 | O | O | DiamIdent | Contains the end point to which the Diameter message is to be routed. |
| Destination-Realm | 283 | M | M | DiamIdent | Contains the realm to which the Diameter message is to be routed. |
| Auth-Application-Id | 258 | M | M | Unsigned32 | Contains the application ID of the Diameter Credit Control Application which is 4. |
| CC-Request-Type | 416 | M | - | Enumerated | Contains the transfer type: event for event based charging and initial, update, terminate for session based charging. |
| User-Name | 1 | O | - | UTF8String | Contains the user name in the format of a NAI according to RFC 6733. |
| Subscription-Id | 443 | O | - | Grouped | Contains the identification of the user that is going to access the service in order to be identified by the OCS. |
| Subscription-Id-Type | 450 | OM | - | Enumerated | Contains the type of the identifier, for example, value 0 is used for the international E.164 format according to ITU-T E.164 numbering plan. This AVP is a member of Subscription-Id Grouped AVP. |
| Subscription-Id-Data | 444 | OM | - | UTF8String | Contains the user data content, for example, the MSISDN. This AVP is a member of Subscription-Id Grouped AVP. |
| Called-Station-Id | 30 | O | - | UTF8String | Contains the Access Point Name (APN) the user is connected to. |
OC-DRA validates all the AVP listed except for those that have already been validated by DCL and DRL prior to the invocation of OC-DRA which include Origin-Host AVP, Origin-Realm AVP and Destination-Realm AVP.
Once validation of the Diameter Request content is complete, OC-DRA performs Diameter Request message processing and routing.
