Location and Congestion reports overview

General information

Location and Congestion reports provide information about loading and congestion at Access Network Locations (ANLs).

Use cases

Congestion control—Use the report to detect traffic congestion patterns. Once these patterns are understood, specific DEM congestion policies can be configured on the MS-ISA or VAA, and measured for their effectiveness in subsequent reports.

Drill-down reports

All reports can be run from the main Location and Congestion reports folder. Some reports can also be run as drill-downs by clicking on a data point in another report.

The following table shows the drill-downs available for Location and Congestion reports. Each level of indentation indicates a drill down. For example, a Top Congested Access Network Locations Details report is a drill-down from a Top Congested Access Network Location report.

Table 6-1: Available drill-downs for Location and Congestion reports

Top Congested Access Network Location

Top Congested Access Network Locations Details

Top Congested Access Network Locations Details

Subscriber and Usage Details for Selected Access Network Location

Top Congested Access Network Locations Geographic Distribution

Subscriber and Usage Details for Selected Access Network Location

Top Loaded Access Network Locations

Top Congested Access Network Locations Details

Top Congested Access Network Locations Details

Subscriber and Usage Details for Selected Access Network Location

Custom table for ANL data

Location and Congestion reports are dependent on a custom table of ANL data on the auxiliary database, analytics_anl_details_table_ct. This table provides a link between MAC addresses and friendly names. The custom table is created automatically. It can be populated using the customData.bash script on the auxiliary database. See the NSP Administrator Guide for more information about using the CustomData script.

If Location and Congestion reports are run when the table is not populated, MAC addresses will appear instead of readable ANL names.

A Top Congested Access Network Locations Geographic Distribution report cannot be run if the analytics_anl_details_table_ct is not populated. Other Location and Congestion reports can be run, but they must be run using the ANL ID or Radio ID if applicable. If the ID is not typed correctly the report will have no data.

Custom table structure

Figure 6-1, Sample analytics_anl_details_table_ct shows a sample table file for the analytics_anl_details_table_ct table. Table 6-2, Custom table structure provides information about the data to include in each column.

Figure 6-1: Sample analytics_anl_details_table_ct
 type, stateOrProv,city,name,id,subtype,radioVLAN,radioSSID,radioFreq,latitude,longitude,manufacturer,model,swFw
1, Nova Scotia, Dartmouth, 4 Middle Street, 0001000200030000BCE0000000000000, 0, 0, 0, 0, 0.0, 0.0, 0, 0, 0
2, British Columbia, Victoria, 700 Victoria Street, 10012002300300000000000000000000, 0, 0, 0, 0, 0.0, 0.0, 0, 0, 0
4, Ontario, Kanata, 600 March Road - AP, 10C12F52B7E700000000000000000000, 1, 0, 00000000, 0, 100.78789, 10.12312, ApplesWorld, iphonesWorld, 0.0
5, British Columbia, Victoria, 700 Victoria_3g , 10012002300300000000000000000000, 0, 0, 0, 0, 0.0, 0.0, 0, 0, 0
6, Ontario, Kanata, 600 March Road -4g, 10C12F52B7E700000000000000000000, 0 , 0, 00000000, 0, 100.78789, 10.12312, ApplesWorld, iphonesWorld, 0.0
Table 6-2: Custom table structure

Column

Data type

Notes

type

integer

  • 0 - Unknown

  • 1 - 3G Iub

  • 2 - 3G Cell

  • 3 - 4G Cell

  • 4 - Wi-Fi access point/radio

  • 5 - 3G-CELL-ULI

    Location information comes from ULI: ULI in this case is CGI (Applicable for Mobile domain)

  • 6- 4G-CELL-ULI

    Location information comes from ULI: ULI in this case is ECGI (Applicable for Mobile domain)

stateOrProv

variable character

The state or province where the ANL is located

city

variable character

The city where the ANL is located

name

variable character

The friendly name to assign the ANL

id

variable character

The access point ID.

The ID is 32 hex digits long, and is composed of the following:

Access point MAC address (12 digits) + VLAN (4 digits) + 16 zeros (0)

If there is no VLAN, enter four zeros (0000).

subtype

integer

For Wi-Fi (type 4), enter 1 for an access point and 0 for a VLAN.

For all other types, the default value of 0 is correct.

radioVLAN

integer

VLAN number

radioSSID

variable character

Radio service set identifier

radioFreq

integer

Radio frequency

latitude

numeric

Latitude of the ANL location

longitude

numeric

Longitude of the ANL location

manufacturer

variable character

Device manufacturer, for example, Apple

model

variable character

Device model, for example, iPhone

swFw

variable character

Software firmware number