Oracle Server E10293-02 ユーザーズマニュアル
Dictionary
Programming Oracle Diameter Applications
B-7
Example B–7
Defining the <returnCode> Element
<dictionary>
<vendor id=
"
10415
"
name=
"
3GPP
"
>
<returnCode name=
"
DIAMETER_USER_UNKNOWN
"
code=
"
5030
"
/>
....
</vendor>
</dictionary>
avp Element
The <avp> element defines an AVP as described in RFC-3588.
The <avp> attributes are:
1.
The avp name attribute is the human-readable name of this AVP.
2.
The avp code attribute defines the integer value used to encode the AVP for
transmission on the network.
transmission on the network.
3.
The avp mandatory attribute defines whether the mandatory bit of this AVP
should or should not be set. Possible values are "must" or "mustnot".
should or should not be set. Possible values are "must" or "mustnot".
4.
The avp protected attribute defines whether the protected bit of this AVP
should or should not be set. Possible values are "may" or "maynot".
should or should not be set. Possible values are "may" or "maynot".
5.
The avp may-encrypt attribute defines whether the AVP has to be encrypted in
case of CMS security usage. Possible values are "yes" or "no".
case of CMS security usage. Possible values are "yes" or "no".
6.
The avp vendor-specific attribute specifies if this is a vendor specific AVP or
not. Possible values are "yes" or "no".
not. Possible values are "yes" or "no".
, the 3GPP vendor extends the dictionary with the AVP
"Application-provided-called-party-address".
Example B–8
Defining the <avp> Element
<dictionary>
<vendor id=
"
10415
"
name=
"
3GPP
"
>
<avp name=
"
Application-provided-called-party-address
"
code=
"
837
"
mandatory=
"
mustnot
"
protected=
"
may
"
may-encrypt=
"
no
"
vendor-specific=
"
yes
"
>
....
</avp>
</vendor>
</dictionary>
The <avp> element regroups either a <type> element or a <grouped> element.
type Element
The <type> element defines the data type of the AVP in which it appears. This
element must appear in all non-grouped AVP definitions.
element must appear in all non-grouped AVP definitions.
The type-name attribute of the <type> element contains the data type name as
defined in RFC-3588: Possible values are:
defined in RFC-3588: Possible values are:
■
"OCTETSTRING"
■
"INTEGER32"
■
"INTEGER64"