Difference between revisions of "Diameter Commands"

Revision as of 16:55, 9 September 2016

This is the main part of the message holding the data specific to each Diameter interface.

The Diameter command is wrapped in a XML element marked by <operation/> to make it easy to find the information in the XML. The child of the <operation/> is an XML describing the Diameter command decoded/to be encoded. The tag of the child element is the name of the command.

Each message can only contain a single Diameter command message.

<m>
    ....  
    <operation>
        <InsertSubscriberDataRequest appid="16777251">
            <DestinationHost>mme.example.com</DestinationHost>
            <DestinationRealm>example.com</DestinationRealm>
            <Username>004100123456789</Username>
            <SubscriptionData vendor="10415">
                <MSISDN vendor="10415">40700100100</MSISDN>
            </SubscriptionData>
            <IDRFlags vendor="10415">eps-user-state-req,eps-loc-info-req,local-tz-req,rat-type-req</IDRFlags>
        </InsertSubscriberDataRequest>
    </operation>
 </m>

Parameters

For the XML child containing the command, the following parameters appear as attributes (bold - mandatory, italic - optional)

• • appid: Numeric identifier of the interface to which this message belongs to
  • flags : Diameter flags for the message. For messages on direction TCP aplication -> Diameter translator, flags are optional in requests/answers(they will be added automatically by Diameter), but if they are added, they must be correctly correlated with the tag. An error answer must set flags to error.

For S6a messages, the application ID is 16777251.

Non-base protocol Diameter AVPs must have vendor identifier set. For 3GPP AVPs this is 10415.