The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Each RDR is sent to the Cisco SCMS Collection Manager. On the Collection Manager, adapters convert the RDRs and store them in database tables. There is a separate table for each RDR type. This chapter presents these tables and their columns (field names and types).
For additional information, such as RDR structure, RDR column, and field descriptions, and how the RDRs are generated, see the "Raw Data Records: Formats and Field Contents" section.
•Table RPT_TOPS_PERIOD0_CUMULATIVE
•Table RPT_TOPS_PERIOD1_CUMULATIVE
•Table RPT_TOPS_PEAK_CUMULATIVE
Each RDR is routed to the appropriate adapter—the Java Database Connectivity (JDBC), Topper/Aggregator (TA), or Real-Time Aggregating (RAG) adapter—converted, and written into a database table row. There is a separate table for each RDR type, with a column designated for each RDR field.
In addition to the RDR fields that are specific to each RDR type, the RPT_NUR, RPT_SUR, RPT_PUR, RPT_LUR, and RPT_TR tables contain two universal columns TIME_STAMP and RECORD_SOURCE. The following values are placed in these two universal columns (field numbers 1 and 2, respectively):
•TIME_STAMP—The RDR time stamp assigned by the SCMS Collection Manager. The field is in UNIX time_t format, which is the number of seconds since midnight of 1 January 1970.
•RECORD_SOURCE—Contains the IP address of the Cisco SCE platform that generated the RDR.
The IP address is in 32-bit binary format (displayed as a 4-byte integer).
Database table RPT_NUR stores data from SUBSCRIBER_USAGE_RDRs.
Note This table is not part of the default configuration.
These RDRs have the tag 4042321920.
Table 4-1 list the columns of Table RPT_NUR.
Database table RPT_SUR stores data from REALTIME_SUBSCRIBER_USAGE_RDRs.
These RDRs have the tag 4042321922.
Table 4-2 list the columns of Table RPT_SUR.
Database table RPT_PUR stores data from PACKAGE_USAGE_RDRs.
These RDRs have the tag 4042321924.
Table 4-3 list the columns of Table RPT_PUR.
Database table RPT_LUR stores data from LINK_USAGE_RDRs.
These RDRs have the tag 4042321925.
Table 4-4 list the columns of Table RPT_LUR.
Database table RPT_GUR stores data from GENERIC USAGE_RDRs.
These RDRs have the tag 4042322064.
Table 4-5 list the columns of Table RPT_GUR.
Database table RPT_TR stores data from TRANSACTION_RDRs.
These RDRs have the tag 4042321936.
Table 4-6 list the columns of Table RPT_TR.
Database table RPT_MEDIA stores data from MEDIA_FLOW_RDRs.
These RDRs have the tag 4042323052.
Table 4-7 list the columns of Table RPT_MEDIA.
Database table RPT_MALUR stores data from MALICIOUS_TRAFFIC_PERIODIC_RDRs.
These RDRs have the tag 4042322000.
Table 4-8 list the columns of Table RPT_MALUR.
The TA adapter generates database table RPT_TOPS_PERIOD0 for its shorter aggregation interval (by default, one hour).
Table 4-9 list the columns of Table RPT_TOPS_PERIOD0.
For each Top Report, the TA adapter sorts the subscriber/consumption pairs from the highest consumption to lowest. At the end of each report is a statistic giving the sum of all subscribers for this metric.
If the report is empty, typically when no traffic is reported for the designated service/metric pair during the aggregation period, the database is updated, but only the final row in the report is updated to show a total consumption of zero. The database is updated to avoid the perception in Cisco SCA Reporter that the report is not generated due to a malfunction.
Table 4-10 list the possible values for the METRIC_ID field.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
2 |
Combined Volume |
3 |
Sessions |
4 |
Seconds |
The TA adapter generates database table RPT_TOPS_PERIOD1 for its longer aggregation interval (by default, 24 hour).
Table 4-11 list the columns of Table RPT_TOPS_PERIOD1.
For each Top Report, the TA adapter sorts the subscriber/consumption pairs from the highest consumption to lowest. At the end of each report is a statistic giving the sum of all subscribers for this metric.
If the report is empty, typically when no traffic was reported for the designated service/metric pair during the aggregation period, the database is still updated, but the only row in the report is the final row showing a total consumption of zero. The database is updated to avoid the perception in the Cisco SCA Reporter that the report is not there because of a malfunction.
Table 4-12 lists the possible values for the METRIC_ID field.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
2 |
Combined Volume |
3 |
Sessions |
4 |
Seconds |
The TA adapter generates database table RPT_TOPS_PERIOD0_CUMULATIVE for its shorter aggregation interval (by default, one hour).
Table 4-13 list the columns of Table RPT_TOPS_PERIOD0_CUMULATIVE.
Table 4-14 list the possible values for the METRIC_ID field.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
The TA adapter generates database table RPT_TOPS_PERIOD1_CUMULATIVE for its longer aggregation interval (by default, one day).
Table 4-15 list the columns of Table RPT_TOPS_PERIOD1_CUMULATIVE.
Table 4-16 lists the possible values for the METRIC_ID field.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
The TA adapter generates database table RPT_TOPS_PEAK_PERIOD for the configured period in the peak_hours section in taadapter.conf.
Table 4-17 lists the columns of the RPT_TOPS_PEAK_PERIOD table.
Table 4-18 lists the possible values for the METRIC_ID field.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
The TA adapter generates database table RPT_TOPS_PEAK_CUMULATIVE for the configured period in the peak_hours section in taadapter.conf.
Table 4-19 lists the columns of the RPT_TOPS_PEAK_CUMULATIVE table.
Table 4-20 lists the possible values for the METRIC_ID field.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
Database table RPT_VLUR stores data from VIRTUAL_LINKS_USAGE_RDRs.
These RDRs have the tag 4042321926.
Table 4-21 lists the columns of the RPT_VLUR table.
Database table INI_VALUES is updated whenever the service configuration is applied to the SCE platform. This table contains, for each SCE IP address, mappings between numeric identifiers and textual representation for services, packages, and other service configuration components. The mapping is represented as a standard properties file in string form, where each mapping file is stored in one row. The SCA Reporter uses the mappings contained in this table.
Table 4-22 lists the columns of the INI_VALUES table.
Possible values for VALUE_TYPE field are:
•1—Service ID/service name
•2—Package ID/package name
•3—TCP port number/port name
•4—Time frame ID/time frame name
•5—SCE address 32-bit/dotted notation
•6—IP protocol number/IP protocol name
•7—Signature protocol ID/protocol name
•8—P2P signature protocol ID/protocol name
•11—Global service usage counter ID/counter name
•12—Subscriber service usage counter ID/counter name
•13—Package usage counter ID/counter name
•15—UDP port number/port name
•16—Policy/Flags
•17—Service Names
•18—All links
•19—Zone name/Zone Id
•20—Zone name/Zone counter
•21—Operating System name/Operating System index
•1002—VoIP protocol family/Protocol name
•1003—Worm protocol family/Protocol name
•1005—Packet Stream Pattern-Based Protocols/Protocol name
•1006—Bundled protocol family/Protocol name
•1007—Unidirectionally Detected protocol family/Protocol name
•1008—RTCP protocol family/Protocol name
•1009—SPAM Detected protocol family/Protocol name
•1010—Behavioral protocol family/Protocol name
•1011—E-mail and Newsgroups protocol family/Protocol v
•1012—Gaming protocol family/Protocol name
•1013—Generic protocol family/Protocol name
•1014—HTTP protocol family/Protocol name
•1015—Instant Messaging protocol family/Protocol name
•1016—Net Admin protocol family/Protocol name
•1017—Video protocol family/Protocol name
•1018—Tunneling protocol family/Protocol name
•1019—ClickStream protocol family/Protocol name
•2001—P2P protocol family/Global Counter name
•2002—VoIP protocol family/Global Counter name
•2003—Worm protocol family/Global Counter name
•2005—Packet Stream Pattern-Based Protocols/Global Counter name
•2006—Bundled protocol family/Global Counter name
•2007—Unidirectionally Detected protocol family/Global Counter name
•2008—RTCP protocol family/Global Counter name
•2009—SPAM Detected protocol family/Global Counter name
•2010—Behavioral protocol family/Global Counter name
•2011—E-mail and Newsgroups protocol family/Global Counter name
•2013—Generic protocol family/Global Counter name
•2014—HTTP protocol family/Global Counter name
•2015—Instant Messaging protocol family/Global Counter name
•2017—Video protocol family/Global Counter name
•2018—Tunneling protocol family/Global Counter name
•2019—ClickStream protocol family/Global Counter name
•3001—P2P protocol family/Subscriber Counter name
•3002—VoIP protocol family/Subscriber Counter name
•3005—Packet Stream Pattern-Based Protocols/Subscriber Counter name
•3007—Unidirectionally Detected protocol family/Subscriber Counter name
•3010—Behavioral protocol family/Subscriber Counter name
•3013—Generic protocol family/Subscriber Counter name
•3014—HTTP protocol family/Subscriber Counter name
•3015—Instant Messaging protocol family/Subscriber Counter name
•3017—Video protocol family/Subscriber Counter name
•3019—Tunneling protocol family/Subscriber Counter name
•4001—P2P protocol family/Signature
•4002—VoIP protocol family/Signature
•4003—Worm protocol family/Signature
•4005—Packet Stream Pattern-Based Protocols/Signature
•4006—Bundled protocol family/Signature
•4007—Unidirectionally Detected protocol family/Signature
•4008—RTCP protocol family/Signature
•4009—SPAM Detected protocol family/Signature
•4010—Behavioral protocol family/Signature
•4011—E-mail and Newsgroups protocol family/Signature
•4012—Gaming protocol family/Signature
•4013—Generic protocol family/Signature
•4014—HTTP protocol family/Signature
•4015—Instant Messaging protocol family/Signature
•4016—Net Admin protocol family/Signature
•4017—Video protocol family/Signature
•4018—Tunneling protocol family/Signature
•4019—ClickStream protocol family/Signature
Database table VLINK_INI is updated when the Collection Manager utility update_vlinks.sh is run. This table contains the name and ID of each virtual link defined in the SCE platform. The SCA Reporter uses the mappings contained in this table for the Virtual Links reports.
Table 4-23 lists the columns of the VLINK_INI table.
Database table CONF_SE_TZ_OFFSET contains the time-zone offset in minutes for the clock of each SCE platform as configured by the select-sce-tz.sh script.
Table 4-24 lists the columns of table CONF_SE_TZ_OFFSET.
|
|
---|---|
TIME_STAMP |
Date_Time |
OFFSET_MIN |
Number |
The RAG adapter generates database table RPT_TOP_APN for the configured aggregation interval (1 hour by default) as configured in vsa_SURs.xml.
Table 4-25 lists the columns of the RPT_TOP_APN table.
At the end of the each aggregation period, the Cisco SCMS Collection Manager inserts the aggregated records into the table. Rank is a sequential numerical value that indicates the top entries. The ranks of VSA attributes are based on usage (downstream, upstream) of particular services.
From the RPT_TOP_APN table, you can generate reports such as Usage per APN and Application Usage per APN.
The RAG adapter generates database table RPT_TOP_DEVICE_TYPE for the configured aggregation interval (1 hour by default) as configured in vsa_SURs.xml.
Table 4-26 lists the columns of the RPT_TOP_DEVICE_TYPE table.
At the end of the each aggregation period, the Collection Manager inserts the aggregated records into the table. Rank is a sequential numerical value that indicates the top entries. RANK_VOLUME is derived based on the usage (downstream, upstream) of particular services. RANK_UNIQ_SUBS is derived based on the total number of unique subscribers on a particular service.
From the RPT_TOP_DEVICE_TYPE table, we can generate reports such as Device Type Distribution (IMEI), Usage per Device, and Application Usage per Device.
The RAG adapter generates database table RPT_TOP_NETWORK_TYPE for the configured aggregation interval (1 hour by default) as configured in vsa_SURs.xml.
Table 4-27 lists the columns of the RPT_TOP_NETWORK_TYPE table.
At the end of the each aggregation period, the Collection Manager inserts the aggregated records into the table. Rank is a sequential numerical value that indicates the top entries. RANK_VOLUME is derived based on the usage (downstream, upstream) of particular services.
From the RPT_TOP_NETWORK_TYPE table, you can generate reports such as Usage per Network Type and Application Usage per Network Type.
The RAG adapter generates database table RPT_TOP_SGSN for the configured aggregation interval (1 hour by default) as configured in vsa_SURs.xml.
Table 4-28 lists the columns of the RPT_TOP_SGSN table.
At the end of the each aggregation period, the Collection Manager inserts the aggregated records into the table. Rank is a sequential numerical value that indicates the top entries. RANK_VOLUME is derived based on the usage (downstream, upstream) of particular services.
From the RPT_TOP_SGSN table, you can generate a Usage per SGSN report.
The RAG adapter generates database table RPT_TOP_USER_LOCATION for the configured aggregation interval (1 hour by default) as configured in vsa_SURs.xml.
Table 4-29 lists the columns of the RPT_TOP_USER_LOCATION table.
At the end of the each aggregation period, the Collection Manager inserts the aggregated records into the table. Rank is a sequential numerical value that indicates the top entries. RANK_VOLUME is derived based on the usage (downstream, upstream) of particular services.
From the RPT_TOP_USER_LOCATION table, you can generate reports such as Number of Subscribers per Location and Usage per Location.
The RAG adapter generates database table RPT_DVLINK. It aggregates the subscriber usage RDR data. Aggregation is based on per package and per VLINK (DOWN VLINK). You can generate a report.
Table 4-30 lists the columns of the RPT_DVLINK table.
The RAG adapter generates database table RPT_UVLINK. It aggregates the subscriber usage RDR data. Aggregation is based on per package and per VLINK (UP VLINK). You can generate a report.
Table 4-31 lists the columns of the RPT_UVLINK table.
The RAG adapter generates database table RPT_TOP_HTTP_DOMAINS for the configured aggregation interval (1 hour by default) as configured in http_TURs.xml. It aggregates the HTTP transaction usage RDR data. Aggregation is based on domain, service, and package. You can generate reports.
Table 4-32 lists the columns of the RPT_TOP_HTTP_DOMAINS table.
At the end of the each aggregation period, the Collection Manager inserts the aggregated records into the table. Rank is a sequential numerical value that indicates the top entries. RANK_VOLUME is derived based on the usage (downstream, upstream), package, and service. RANK_SESSIONS is derived based on the total sessions, package, and service. RANK_UNIQ_SUBS is derived based on the total number of unique subscribers, package, and service.
The RAG adapter generates database table RPT_TOP_HTTP_HOSTS for the configured aggregation interval (1 hour by default) as configured in http_TURs.xml. It aggregates the HTTP transaction usage RDR data. Aggregation is based on domain, service, and package. You can generate reports.
Table 4-33 lists the columns of the RPT_TOP_HTTP_HOSTS table.
At the end of the each aggregation period, the Collection Manager inserts the aggregated records into the table. Rank is a sequential numerical value that indicates the top entries. RANK_VOLUME is derived based on the usage (downstream, upstream), package, and service. RANK_SESSIONS is derived based on the total sessions, package, and service. RANK_UNIQ_SUBS is derived based on the total number of unique subscribers, package, and service.
The RAG adapter generates database table RPT_TOP_VIDEO_DOMAINS for the configured aggregation interval (1 hour by default) as configured in video_TURs.xml. It aggregates the video transaction usage RDR data. Aggregation is based on domain, service, and package. You can generate reports.
Table 4-34 lists the columns of the RPT_TOP_VIDEO_DOMAINS table.
At the end of the each aggregation period, the Collection Manager inserts the aggregated records into the table. Rank is a sequential numerical value that indicates the top entries. RANK_VOLUME is derived based on the usage (downstream, upstream), package, and service. RANK_SESSIONS is derived based on the total sessions, package, and service. RANK_UNIQ_SUBS is derived based on the total number of unique subscribers, package, and service.
The RAG adapter generates database table RPT_TOP_VIDEO_HOSTS for the configured aggregation interval (1 hour by default) as configured in video_TURs.xml. It aggregates the video transaction usage RDR data. Aggregation is based on domain, service, and package. You can generate reports.
Table 4-35 lists the columns of the RPT_TOP_VIDEO_HOSTS table.
At the end of the each aggregation period, the Collection Manager inserts the aggregated records into the table. Rank is a sequential numerical value that indicates the top entries. RANK_VOLUME is derived based on the usage (downstream, upstream), package, and service. RANK_SESSIONS is derived based on the total sessions, package, and service. RANK_UNIQ_SUBS is derived based on the total number of unique subscribers, package, and service.
The RPT_ZUR database table stores data from ZONE_USAGE_RDRs.
These RDRs have the tag 4042321928.
Table 4-36 lists the columns of the RPT_ZUR table.
The RPT_SPAM database table stores data from SPAM_RDRs.
These RDRs have the tag 4042322048.
Table 4-37 lists the columns of the RPT_SPAM table.
The RPT_SPAM database table stores data from Online_Flow_Usage_RDRs.
These RDRs have the tag 4042321927.
Table 4-38 lists the columns of the RPT_FUR table.
The IMEI_DEVICETYPE database table contains mappings for the device types with IMEI_TAC. The Reporter uses the IMEI_TAC column for the Device Type Reports.
Table 4-39 lists the columns of the IMEI_DEVICETYPE table.
|
|
---|---|
TIME_STAMP |
Timestamp |
IMEI_TAC |
String |
DEVICE_TYPE |
String |