Difference between revisions of "Diameter Common features"

Latest revision as of 13:52, 9 September 2016

Messages are represented hierarchically in XML format. There may be more parameters than described in this specification. Unknown parameters should be ignored.

Each message contains 3 major parts:

• Latency related information
• Diameter information regarding identification and transport
• Diameter command

In XML these map like in this example:

<m>

    <timestamp-recv>1470663005862835</timestamp-recv>
    <diameter>
        <timeout>60000</timeout>
        <local_node>example.com/hss.example.com</local_node>
        <trans_id>hss/123456</trans_id>
    </diameter>
    <operation>
        <InsertSubscriberDataRequest appid="16777251" flags="request,proxiable">
            <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>

In these examples the XML is nicely indented for readability. In practice any whitespace between XML elements may be omitted.