> UDR Format Configuration Mode Commands
> The UDR Format Configuration Mode enables configuring User Detail Record (UDR) formats. UDR file formats are represented in Comma Separated Value (CSV).
> Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
> attribute
> This command specifies the order of fields in the UDR.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> attribute attribute { [ format { MM/DD/YY-HH:MM:SS | MM/DD/YYYY-HH:MM:SS | YYYY/MM/DD-HH:MM:SS | YYYYMMDDHHMMSS | seconds } [ localtime ] | [ { bytes | pkts } { downlink | uplink } ] ] priority priority }
> no attribute attribute [ priority priority ]
> no
> Removes the specified attribute configuration.
> attribute
> Specifies the attribute.
> attribute must be one of the following:

> Attribute | Description
> diameter-session-id | Unique Diameter session identifier. Important: This attribute is customer specific, and is only available in 8.3 and later releases.
> radius-called-station-id | Called Station ID of the mobile handling the flow.
> radius-calling-station-id | Calling Station ID of the mobile handling the flow.
> radius-fa-nas-identifier | RADIUS NAS identifier of Foreign Agent (FA).
> radius-fa-nas-ip-address | RADIUS IP address of Foreign Agent (FA).
> radius-nas-identifier | RADIUS NAS identifier.
> radius-nas-ip-address | RADIUS NAS IP address. Important: This attribute is interchangeable with sn-st16-ip-addr for the user.
> radius-user-name | User name associated with the flow.
> sn-3gpp2-bsid | This option is obsolete. To configure this attribute see the rule-variable command.
> sn-3gpp2-carrier-id | This option is obsolete. To configure this attribute see the rule-variable command.
> sn-3gpp2-esn | This option is obsolete. To configure this attribute see the rule-variable command.
> sn-3gpp2-meid | This option is obsolete. To configure this attribute see the rule-variable command.
> sn-3gpp2-service-option | This option is obsolete. To configure this attribute see the rule-variable command.
> sn-acct-beginning-session | Session beginning information. Important: This attribute is customer specific, and is only available in 8.3 and later releases.
> sn-acct-session-continue | Session continue information. Important: This attribute is customer specific, and is only available in 8.3 and later releases.
> sn-acct-session-id | Indicator for the Accounting Session Identifier.
> sn-acct-session-time | Duration from acct-status-type:start to acct-status-type:stop. Important: This attribute is customer specific, and is only available in 8.3 and later releases.
> sn-acct-status-type | Accounting status identifier. Important: This attribute is customer specific, and is only available in 8.3 and later releases.
> sn-charging-type | Charging type:
> • | offline
> • | online
> Important: This attribute is customer specific, and is only available in 8.3 and later releases.
> sn-closure-reason | Includes reason for the termination of the flow/UDR:
> • | 0 = CALL_TERMINATION — normal, i.e., subscriber session ended
> • | 1 = PDSN_HO — handoff control processing specified
> • | 2 = TIME_LIMIT
> • | 3 = VOLUME_LIMIT
> • | 4 = MGMT_INTERVENTION
> • | 5 = ACCT_SESS_START
> • | 6 = CCRU_RESPONSE
> • | 7 = OFFLINE_CHARGING — for UDRs generated when offline charging trigger is received from DCCA
> sn-content-id | Unique identifier for the content-id.
> sn-content-label | Identifier for text label for content-id.
> sn-content-vol | Identifier for content volume.
> sn-correlation-id | RADIUS correlation identifier.
> sn-duration | Time difference between the first and last packet of a single data flow accounted in the UDR record. I.e., the time difference between the first ICMP echo request and the last ICMP echo response before the record gets written for the content-id.
> sn-end-time [ format format] | Timestamp for last packet of flow in UTC.
> sn-fa-correlation-id | RADIUS Correlation Identifier of the Foreign Agent (FA).
> sn-fa-ip-address | FA IP address.
> sn-filler-blank | Keeps attributes place blank and generates an empty UDR field.
> sn-filler-zero | Fills ‘0’ for this attribute place in the EDR/UDR.
> sn-format-name | Indicates the name of the UDR/EDR format used.
> sn-group-id | Indicates the sequence group identifier for the records.
> sn-ha-ip-address | Home Agent IP address. Important: This attribute is customer specific, and is only available in 8.3 and later releases.
> sn-local-seq-no | Unique local sequence number of UDR identifier per ACSMgr/SessMgr and linearly increasing in UDR file.
> sn-ocs-ip-address | Online Charging Server's IP address. Important: This attribute is customer specific, and is only available in 8.3 and later releases.
> sn-rulebase | Indicates the name of the ACS rulebase used.
> sn-sequence-no | Unique sequence number (per sn-sequence -group and radius-nas-ip-address) of UDR identifier and linearly increasing in UDR file.
> sn-served-bsa-addr | Indicator for address of Base Station Area being served.
> sn-service-name | Indicator for ACS service name.
> sn-st16-ip-addr | IP address of the chassis handling this flow. Important: This attribute is interchangeable with radius-nas-ip-address for other systems.
> sn-start-time [ format format ] | Timestamp for first packet of flow in UTC.
> sn-stream-number | Unique UDR billing record identifier. Important: This attribute is customer specific, and is only available in 8.3 and later releases.
> sn-subscriber-id | Indicator for subscriber ID.
> sn-subscriber-nat-flow-ip | NAT IP address(es) of NAT-enabled subscriber.
> sn-timestamp | Timestamp when the UDR is actually generated. Important: This attribute is customer specific, and is only available in 8.3 and later releases.

> ‌
> format { MM/DD/YY-HH:MM:SS | MM/DD/YYYY-HH:MM:SS | YYYY/MM/DD-HH:MM:SS | YYYYMMDDHHMMSS | seconds }
> Specifies the timestamp format.
> localtime
> Specifies the local time. By default, timestamps are displayed in GMT.
> { bytes | pkts } { downlink | uplink }
> Specifies bytes/packets sent/received from/by mobile.
> priority priority
> Specifies the position priority of the value within the UDR. Lower numbered priorities (across all attribute, event-label, and rule-variable) occur first.
> priority must be an integer from 1 through 65535. Up to 50 position priorities (across all attribute, event-label, and rule-variable) can be configured.
> Usage
> Use this command to set the attributes and priority for UDR file format.
> A particular field in UDR format can be entered multiple times at different priorities. While removing the UDR field using the no attribute command either you can remove all occurrences of a particular field by specifying the field name or a single occurrence by additionally specifying the optional priority keyword.
> Consider the following scenario. If the volume/time threshold interval is large enough (or disabled). At time t=0, 10 ICMP packets are sent, which takes 9 seconds. There is nothing for the next 100 seconds, and then again 10 ICMP packets are sent which takes 10 seconds, and then again nothing for next the 60 seconds and then the session is terminated.
> In this scenario:

> • | sn-start-time should be t = 0.

> • | sn-end-time should be t = 0+9+100+10 (sn-end-time would be the last ICMP packet sent).

> • | sn-duration should be sn-end-time minus sn-start-time, i.e. 0+9+100+10 – 0 = 119 seconds (since the ICMP flow would exist between the two intervals of sending ICMP packets, the sn-start-time would be that of the first packet of the flow and sn-end-time of the last packet (20th packet). Hence, sn-duration would take into account all the seconds between the first and last packet of the flow).

> Example
> The following is an example of this command:
> attribute radius-user-name priority 12
> end
> Exits the current configuration mode and returns to the Exec mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Use this command to return to the Exec mode.
> event-label
> This command configures an optional event ID to use in generated billing records.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> event-label label priority priority
> no event-label
> no
> Removes the previously configured event label for UDR attribute.
> label
> Specifies event label for attribute to be used for UDR format.
> label must be an alpha and/or numeric string of 1 through 63 characters in length.
> priority priority
> Specifies the CSV position of event ID in UDR.
> priority must be an integer from 1 through 65535.
> Usage
> Use this command to set the event ID and its position in UDR file format.
> Example
> The following is an example of this command:
> event-label radius_csv1 priority 23
> exit
> Exits the current mode and returns to the parent configuration mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Use this command to return to the parent configuration mode.
> rule-variable
> This command specifies the order of fields in the UDR.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> rule-variable protocol rule priority priority
> no rule-variable [ priority priority ] protocol rule
> no
> Removes the rule-variable protocol configuration.
> protocol rule
> Specifies the rule variable for UDR format.
> protocol must be one of the following with specified rule:

> • | bearer 3gpp2: Bearer-related configuration:

> • | always-on

> • | bsid

> • | carrier-id

> • | esn

> • | ip-qos

> • | ip-technology

> • | meid

> • | release-indicator

> • | serv-MDN

> • | service-option

> • | session-begin

> • | session-continue

> Important: For more information on protocol-based rules see the ACS Ruledef Configuration Mode Commands chapter.
> priority priority
> Specifies the CSV position of the value in the UDR.
> priority must be an integer from 1 through 65535.
> Usage
> Use this command to set the rule variables priority for UDR file format.
> A particular field in UDR format can be entered multiple times at different priorities. While removing the UDR field using the no rule-variable command either you can remove all occurrences of a particular field by specifying the field name or a single occurrence by additionally specifying the optional priority keyword.
> Example
> The following is an example of this command:
> rule-variable bearer 3gpp2 bsid priority 36

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883