Nokia NSS M13.5 VN Functional Specification

Data Export Date: 07 Sep 2008

• 1. Change History
• 2. Document References
• 3. Outstanding Issues
• 4. Network Model
• 4.1 Network Objects
• 4.2 Reference Objects
• 5. Busy Hours
• 6. Constants
• 7. Performance Indicators
• 8. Database Schema
• 8.1 NC Tables
• 8.2 Raw Tables
• 8.3 Views
• 9. Performance Alarms
• 10. Reports
• 11. Data Availability

None.

This section describes the network objects (logical and physical) that are referenced in this technology pack's data model.

HLR

The Home Location Register is the main network database (may be distributed). The HLR records permanent subscriber information, and keeps track of each subscriber's status and location in the network.

LAC

Location/Paging Area Code; a group of cells, managed by an MSC, that a mobile station's location may be recorded against.

MSC

The Mobile Switching Centre has circuit/voice switching functions, as well as linking several BSCs to the core network and managing some of their functions (eg inter-BSC handover). It is also connected to an SS7 network for database queries.

Network

Network information.

Processor

The Processor object represents a CPU inside another network element. Some elements have more than one Processor.

Region

A user defined grouping of network elements.

Route_IF

For each logical Route Interface, there will be 2 entries - 1 for the interface at each end, as it is the interfaces that report the data. Routes may connect switches and other nodes (including BSCs) in a circuit-switched network.

Signalling_LinkSet

A set of Signalling Links between two points.

Signalling_Link

The SS7 Signalling data link is a full-duplex, digital transmission channel, usually operating at 64 kbit/s.

Signalling_Point

Represents a signalling entity that is part of a Node.

Signalling_RouteSet

A Signalling Route is a path from one point to another in the signalling network. It is implemented by a number of LinkSets, but the relationship between RouteSets and LinkSets is not available in the data supplied by most vendors.

VLR

The Visitor Location Register is distributed, and one VLR is usually associated with each MSC. It caches a subset of the information from the HLR, for subscribers that connected locally, plus some other temporary information.

This section describes the reference objects that are used only as lookups for compound-keyed raw data.

Completion_Code

Call completion codes for voice switches.

Supplementary_Service

Supplementary Services supported by voice switches.

Traffic_Type

Types of traffic carried by a voice switch.

This section lists the busy hours that are defined in this technology pack, grouped by the network object to which they relate, as follows:

• HLR
• MSC
• Processor
• Route_IF
• Signalling_Link
• Signalling_LinkSet
• VLR

This section lists all constants that are defined in this technology pack, and which may be referenced in KPI expressions.

This section lists the performance indicators (both one-to-one counter mappings, and complex KPIs) that are defined in this technology pack, grouped by the network object to which they relate, as follows:

• HLR
• LAC
• MSC
• Processor
• Route_IF
• Signalling_Link
• Signalling_LinkSet
• Signalling_Point
• Signalling_RouteSet
• VLR

Note that all KPIs will have total, average, minimum and maximum values calculated for daily, weekly, and monthly summaries. Individual groups of KPIs may have additional summary types (including busy hours) applied to them, and these are listed against the respective KPIs in the tables below.

• HLR.Neutral.GSM.access
• HLR.Neutral.GSM.mobility

HLR.Neutral.GSM.access

Statistics on authentication procedures

HLR.Neutral.GSM.mobility

Statistics on the communication between VLRs and the HLR

• LAC.Neutral.GSM.mobility
• LAC.Neutral.GSM.page

LAC.Neutral.GSM.mobility

The results of updates from or within a Location Area (LA)

LAC.Neutral.GSM.page

The results of paging activity within a Location Area

• MSC.Neutral.GSM.call_completion
• MSC.Neutral.GSM.call_setup
• MSC.Neutral.GSM.destination
• MSC.Neutral.GSM.handover
• MSC.Neutral.GSM.page
• MSC.Neutral.GSM.services
• MSC.Neutral.GSM.traffic.total_switched_traffic
• MSC.Neutral.GSM.traffic

MSC.Neutral.GSM.call_completion

How many of the calls controlled by this MSC terminated with each of the available Completion Codes (CCs)

MSC.Neutral.GSM.call_setup

The call setup performance for calls originating or terminating at an MS in the BSS controlled by this MSC

The performance data measurements for this KPI group are recorded against the combination of MSC and Completion_Code (cc_id)

MSC.Neutral.GSM.destination

The calls managed by an MSC to a particular destination MSC

MSC.Neutral.GSM.handover

The results of handovers passing through this MSC, either (a) to or from a different MSC, or (b) between two BSCs controlled by this MSC

MSC.Neutral.GSM.page

The Paging activity to Mobiles in the BSS controlled by this MSC

MSC.Neutral.GSM.services

The usage of a Supplementary Service (SS) on an MSC. These are sometimes reported by the HLR, but are associated with an MSC in this data model

The performance data measurements for this KPI group are recorded against the combination of MSC and Supplementary_Service (service_id)

MSC.Neutral.GSM.traffic.total_switched_traffic

The call-switching performance of the MSC for a all switched traffic types

MSC.Neutral.GSM.traffic

The call-switching performance of the MSC for a particular traffic type

The performance data measurements for this KPI group are recorded against the combination of MSC and Traffic_Type (traffic_type_id)

• Processor.Neutral.GSM.cpu

Processor.Neutral.GSM.cpu

The performance (load or utilisation) of the CPU

• Route_IF.Neutral.GSM.transmission.forecast
• Route_IF.Neutral.GSM.transmission

Route_IF.Neutral.GSM.transmission.forecast

The forecast performance of the Route

Route_IF.Neutral.GSM.transmission

The performance of the Route as seen from this end (Interface), reported by an MSC

• Signalling_Link.Neutral.GSM.link

Signalling_Link.Neutral.GSM.link

The performance of an individual Signalling Link

• Signalling_LinkSet.Neutral.GSM.forecast
• Signalling_LinkSet.Neutral.GSM.signalling_linkset

Signalling_LinkSet.Neutral.GSM.forecast

The forecast performance of a set of Signalling Links

Signalling_LinkSet.Neutral.GSM.signalling_linkset

The performance of a set of Signalling Links

• Signalling_Point.Neutral.GSM.signalling_point

Signalling_Point.Neutral.GSM.signalling_point

The signalling network?s performance, as seen from a Signalling Point

• Signalling_RouteSet.Neutral.GSM.routeset

Signalling_RouteSet.Neutral.GSM.routeset

The performance of a set of Signalling Routes

• VLR.Neutral.GSM.mobility

VLR.Neutral.GSM.mobility

The Mobility management activity (e.g. Location Area updates) in the BSS controlled by this VLR

This section lists the hierarchy ("NC") tables that are included in this technology pack's database schema.

nc_hlr

nc_lac

nc_msc

nc_network

nc_processor

nc_region

nc_route

nc_ss7_link

nc_ss7_linkset

nc_ss7_point

nc_ss7_routeset

nc_vlr

nc_msc_completion_codes

nc_msc_supplementary_services

nc_msc_traffic_types

nc_hlr_sec

nc_lac_sec

nc_msc_sec

nc_network_sec

nc_processor_sec

nc_region_sec

nc_route_sec

nc_ss7_link_sec

nc_ss7_linkset_sec

nc_ss7_point_sec

nc_ss7_routeset_sec

nc_vlr_sec

This section lists the performance tables that are included in this technology pack's database schema, grouped by the network object to which they relate, as follows:

• HLR
• LAC
• MSC
• Processor
• Route_IF
• Signalling_Link
• Signalling_LinkSet
• Signalling_Point
• Signalling_RouteSet
• VLR

hlr_resource_access_raw

lac_resource_access_raw

msc_call_completion_raw

msc_call_destinations_raw

msc_call_setup_raw

msc_handover_results_raw

msc_resource_pages_raw

msc_supplementary_services_raw

msc_traffic_raw

processor_cpu_raw

route_interface_transmission_raw

ss7_link_availability_raw

ss7_link_performance_raw

ss7_link_utilisation_raw

ss7_linkset_raw

ss7_point_raw

ss7_routeset_raw

vlr_resource_mobility_raw

This section lists the views that are included in this technology pack's database schema.

nc_processor_bsc_v

SELECT nc_id,
processor_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
processor_name,
processor_type,
technology,
vendor,
processor_version
FROM nc_processor
WHERE LOWER(node_type) = "bsc";

nc_processor_ggsn_v

SELECT nc_id,
processor_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
processor_name,
processor_type,
technology,
vendor,
processor_version
FROM nc_processor
WHERE LOWER(node_type) = "ggsn";

nc_processor_hlr_v

SELECT nc_id,
processor_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
processor_name,
processor_type,
technology,
vendor,
processor_version
FROM nc_processor
WHERE LOWER(node_type) = "hlr";

nc_processor_msc_v

SELECT nc_id,
processor_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
processor_name,
processor_type,
technology,
vendor,
processor_version
FROM nc_processor
WHERE LOWER(node_type) = "msc";

nc_processor_sgsn_v

SELECT nc_id,
processor_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
processor_name,
processor_type,
technology,
vendor,
processor_version
FROM nc_processor
WHERE LOWER(node_type) = "sgsn";

nc_ss7_link_bsc_v

SELECT nc_id,
ss7_link_id,
ss7_linkset_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
adjacent_node_id,
data_rate,
ss7_link_name,
technology
FROM nc_ss7_link
WHERE LOWER(node_type) = "bsc";

nc_ss7_link_mgw_v

SELECT nc_id,
ss7_link_id,
ss7_linkset_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
adjacent_node_id,
data_rate,
ss7_link_name,
technology
FROM nc_ss7_link
WHERE LOWER(node_type) = "mgw";

nc_ss7_link_msc_v

SELECT nc_id,
ss7_link_id,
ss7_linkset_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
adjacent_node_id,
data_rate,
ss7_link_name,
technology
FROM nc_ss7_link
WHERE LOWER(node_type) = "msc";

nc_ss7_linkset_bsc_v

SELECT nc_id,
ss7_linkset_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
adjacent_node_id,
data_rate,
designed_link_failures,
ss7_linkset_name,
technology
FROM nc_ss7_linkset
WHERE LOWER(node_type) = "bsc";

nc_ss7_linkset_mgw_v

SELECT nc_id,
ss7_linkset_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
adjacent_node_id,
data_rate,
designed_link_failures,
ss7_linkset_name,
technology
FROM nc_ss7_linkset
WHERE LOWER(node_type) = "mgw";

nc_ss7_linkset_msc_v

SELECT nc_id,
ss7_linkset_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
adjacent_node_id,
data_rate,
designed_link_failures,
ss7_linkset_name,
technology
FROM nc_ss7_linkset
WHERE LOWER(node_type) = "msc";

nc_ss7_point_bsc_v

SELECT nc_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
ss7_point_name,
adjacent_node_id,
technology
FROM nc_ss7_point
WHERE LOWER(node_type) = "bsc";

nc_ss7_point_mgw_v

SELECT nc_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
ss7_point_name,
adjacent_node_id,
technology
FROM nc_ss7_point
WHERE LOWER(node_type) = "mgw";

nc_ss7_point_msc_v

SELECT nc_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
ss7_point_name,
adjacent_node_id,
technology
FROM nc_ss7_point
WHERE LOWER(node_type) = "msc";

nc_ss7_routeset_bsc_v

SELECT nc_id,
ss7_routeset_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
adjacent_node_id,
ss7_routeset_name,
technology
FROM nc_ss7_routeset
WHERE LOWER(node_type) = "bsc";

nc_ss7_routeset_mgw_v

SELECT nc_id,
ss7_routeset_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
adjacent_node_id,
ss7_routeset_name,
technology
FROM nc_ss7_routeset
WHERE LOWER(node_type) = "mgw";

nc_ss7_routeset_msc_v

SELECT nc_id,
ss7_routeset_id,
ss7_point_id,
node_id,
region_id,
network_id,
timestamp,
node_name,
node_type,
adjacent_node_id,
ss7_routeset_name,
technology
FROM nc_ss7_routeset
WHERE LOWER(node_type) = "msc";

This section shows details of the performance alarms that are defined in this technology pack:

None.

This section shows details of the reports that are defined in this technology pack:

Historical Route Traffic Report

This report shows key route traffic statistics for a single route over all the weeks in the forecast base range. The report shows available & defined circuits, % congestion, carried traffic, offered traffic, lost traffic, critical traffic, 3-DAV and 5-DAV traffic, % utilisation and grade of service. The report is always generated with weekly busy hour values.

Overview

Report Parameters

Report Components

HLR Subscribers Graph

This graph shows the number of attached users and the % number of registered users attached.

Overview

Report Parameters

Report Components

Interconnect Traffic Graph

This graph shows the total traffic profile for all routes connecting an MSC to a POI (a POI route).

Overview

Report Parameters

Report Components

Inter-switch Traffic Graph

This graph shows the total traffic profile for all routes connecting an MSC to an MSC (a trunk route).

Overview

Report Parameters

Report Components

LAC Paging Graph

This shows the performance of LAC paging attempts within a Location Area

Overview

Report Parameters

Report Components

Linkset Availability Report Link KPIs

This report shows the availability of a set of linksets and failures and unavailability on the constituent links.

Overview

Report Parameters

Report Components

Linkset Availability Report Linkset KPIs

This report shows the availability of a set of linksets and failures

Overview

Report Parameters

Report Components

Linkset Utilisation Report

This report shows the utilisation of a set of linksets through the traffic carried on their constituent links.

Overview

Report Parameters

Report Components

MSC Calls Graph

This graph shows network incoming and mobile originating call statistics for the specified MSC over the selected days.

Overview

Report Parameters

Report Components