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 Raw Data Record (RDR) is sent to the Cisco Service Control Management Suite (SCMS) Collection Manager (CM). On the CM, 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 Raw Data Records: Formats and Field Contents.
•Table RPT_TOPS_PERIOD0_CUMULATIVE
•Table RPT_TOPS_PERIOD1_CUMULATIVE
•Table RPT_TOPS_PEAK_CUMULATIVE
Each RDR is routed to the appropriate adapter—the 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-CM. 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 Service Control Engine (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 for 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 for 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 for 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 for 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 for Table RPT_GUR.
Database table RPT_TR stores data from TRANSACTION_RDRs.
These RDRs have the tag 4042321936.
Table 4-6 list the Columns for 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 for 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 for Table RPT_MALUR.
The Topper/Aggregator (TA) Adapter generates database table RPT_TOPS_PERIOD0 for its shorter aggregation interval (by default, one hour).
Table 4-9 list the Columns for 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 DB is updated, but the only the final row in the report is updated to show a total consumption of zero. The DB is updated to avoid the perception in Cisco Service Control Application (SCA) Reporter that the report is not generated due to a malfunction.
Table 4-10 list the possible values for the field METRIC_ID.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
2 |
Combined Volume |
3 |
Sessions |
4 |
Seconds |
The Topper/Aggregator (TA) Adapter generates database table RPT_TOPS_PERIOD1 for its longer aggregation interval (by default, 24 hour).
Table 4-11 list the Columns for 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 DB is still updated, but the only row in the report is the final row showing a total consumption of zero. The DB is updated to avoid the perception in the SCA Reporter that the report is not there because of a malfunction.
Table 4-12 lists the possible values for the field METRIC_ID.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
2 |
Combined Volume |
3 |
Sessions |
4 |
Seconds |
The Topper/Aggregator (TA) Adapter generates database table RPT_TOPS_PERIOD0_CUMULATIVE for its shorter aggregation interval (by default, one hour).
Table 4-13 list the Columns for Table RPT_TOPS_PERIOD0_CUMULATIVE.
Table 4-14 list the possible values for the field METRIC_ID.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
The Topper/Aggregator (TA) Adapter generates database table RPT_TOPS_PERIOD1_CUMULATIVE for its longer aggregation interval (by default, one day).
Table 4-15 list the Columns for Table RPT_TOPS_PERIOD1_CUMULATIVE.
Table 4-16 lists the possible values for the field METRIC_ID.
|
|
---|---|
0 |
Up Volume |
1 |
Down Volume |
The Topper/Aggregator (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 for 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 Topper/Aggregator (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 for 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 for 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 for the INI_VALUES table.
Database table VLINK_INI is updated when the CM 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 for table VLINK_INI.
Database table CONF_SE_TZ_OFFSET contains the time-zone offset in minutes for each SCE platform's clock as configured by the select-sce-tz.sh script
Table 4-24 lists the columns for table CONF_SE_TZ_OFFSET.
|
|
---|---|
TIME_STAMP |
Date_Time |
OFFSET_MIN |
Number |
The Real-Time Aggregating (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 for the RPT_TOP_APN 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 of VSA attributes are based on the 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 Real-Time Aggregating (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 for 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 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 Real-Time Aggregating (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 for 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, we can generate reports such as usage per network type and application usage per network type.
The Real-Time Aggregating (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 for 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 Real-Time Aggregating (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 for 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 Real-Time Aggregating (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 for the RPT_DVLINK table.
The Real-Time Aggregating (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 for the RPT_UVLINK table.
The Real-Time Aggregating (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 for 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 Real-Time Aggregating (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 for 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 Real-Time Aggregating (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 for 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 Real-Time Aggregating (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 for 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 for 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 for the RPT_SPAM table.
These RDRs have the tag 4042321927.
Table 4-38 lists the columns for 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 for the IMEI_DEVICETYPE table.
|
|
---|---|
TIME_STAMP |
Timestamp |
IMEI_TAC |
String |
DEVICE_TYPE |
String |