Inbound Roaming Portal

Inbound Overview
Description of the
KPIs and graphical
Inbound Overview elements
Inbound
The purpose of the overview is to show the number of outbound roamers and the traffic. The Roamers
Overview shows If the roamers attaches and if they produce traffic, this is a good indication that the Attached
roaming is working. In addition the trend graphs shows upper and lower bound values that are All users
used to detect abnormal trends. By checking that the top destinations have attached roamers and that have an
generate traffic will ensure that the most important destinations are supervised. failure
based on
The tree maps with the nested rectangle show the % of affected users, the size of the rectangle is one of the
the number of outbound roamers and the color will indicate how many subscribers that have following
problems and are affected. definitions
are
regarded as
affected:
Data
Volume
SMS
Volume
Call Minutes
Affected
Roamers by
cell
KPIs

Other Views:

Location of Inbound
Roamers
Lost inbound roamer cell!

Description of the KPIs and graphical elements

Inbound Roamers Attached

Purpose:
Show how many subscibers that are inbound and are attached to a network.

A snapshot of how many roamers that are inbound, the snapshot is taken each hour.
Each inbound subscriber are stored in an internal "HLR" together with the VPLMN. The subscriber
will be marked as outbound and stored in the "HLR" if the subscriber is successfully attached to a
VPLM.
To be marked as attached one of the following attach procedures shall be sucesfull: MAP Update
Locations (UL), MAP Update Location GPRS or S6a Update Location (LTE).
The subscribers are removed from the "HLR" in case of a Cancel Location.
The following procedures will remove the subscriber from the "HLR": MAP Cancel Location, MAP
Purge MS, MAP Reset, S6a Cancel location, S6a Purge MS, S6a Reset.
If no activity is seen for the inbound roamer in the last 14 Days it is assumed it is not roaming
anymore and the subscriber is removed from the "HLR".

Active Roamers

Purpose:
Shows the number of subscribers that have had any activity during the last period.

Activity is defined as any Inbound Roaming event detected on

Map (2G/3G) - SMS
RANAP (3G) this is captured on the IuCS/IuPS interface from the RNC.
BSSAP (2G) this captured on the Aif/Gb interface from the BSC.
S1AP (4G) this is capture from the MME.
GRX - Any user data sent uplink or downlink for a subscriber.

Affected User

Purpose:
Show how many subscribers that have problem last hour.

All users that have an failure based on one of the following definitions are
regarded as affected:

Attach Problems:

1. MAP Update Locations (UL)

Failed are determined by UL that are not successful excluding roaming steering and
roaming not allowed.
Map Errors that not considered as failures:
MAP Error 1, Unknown Subscriber
MAP Error 5, Unidentified Subscriber
MAP Error 8, Roaming Not Allowed
MAP Error 34, System Failure
MAP Error 35, Data Missing
MAP Error 36, Unexpected Data Value

2. MAP Update Location GPRS

Failed are determined by UL that are not successful excluding roaming steering and
roaming not allowed.
Map Errors that not considered as failures:
MAP Error 1, Unknown Subscriber
MAP Error 5, Unidentified Subscriber
MAP Error 8, Roaming Not Allowed
MAP Error 34, System Failure
MAP Error 35, Data Missing
MAP Error 36, Unexpected Data Value
 3. S6a Update Location (LTE)
Failed are determined by UL that are not successful excluding roaming steering and
roaming not allowed.
DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION (5420)
DIAMETER_ERROR_RAT_NOT_ALLOWED (5421)
DIAMETER_ERROR_ROAMING_NOT_ALLOWED (5004)
(reference IR.88)

Call failures:

Calls that fails in the call setup or dropping during the call in 2G or 3G. The logic is based on:

1. BSSMAP cause
2. RANAP cause
3. CC cause
4. DTAP cause
5. Clear cause
6. Assignment cause
7. RAN cause and
8. the disconnecting node.

Call setup failures for MO calls:

MOBILE ORIGINATING CALL with service type MOBILE ORIGINATING CALL (0001),
EMERGENCY CALL (0010) and VIDEO CALL during CM SERVICE REQUEST that do not
receive an ALERT or direct CONECT message.

Call drops for MO calls:

MOBILE ORIGINATING CALLS with service type MOBILE ORIGINATING CALL (0001),
EMERGENCY CALL (0010) and VIDEO CALL during CM SERVICE REQUEST reaching
CONVERSATIONAL MODE (CONNECT) and abnormally released, e.g. CLEAR
REQUEST or Iu RELEASE REQUEST.

Call setup failures for MT calls:

MOBILE TERMINATING CALL reaching SETUP MESSAGE for VIDEO and VOICE that do
not receives an ALERT or direct CONNECT message + PAGING RESPONSES which
service can’t be determined (MT-UNKNOWN)

Call drops for MT calls:

MOBILE TERMINATING CALLS for VOICE and VIDEO reaching CONVERSATIONAL
MODE (CONNECT) and abnormally released, e.g. CLEAR REQUEST or Iu RELEASE
REQUEST.

Data Problems:

1. Create Session on s6a using GTPv2 (LTE) that are not successful, excluding:
16, Request Accepted.
17, Request Accepted partially.
18, New PDN type due to network preference.
19, New PDN type due to a single address bearer only.
2. Create PDP on Gp using GTPv1 (3G/2g) that are not successful.
Everything not having Cause 128; Request accepted,
Data Volume

Data Volume (MB)

Any user data sent uplink or downlink for a subscriber on ther GPRS roaming exchange (GRX).
Calculation of the Data Volume (MB) = (Uplink Bytes + Downlink Bytes )/(1024*1024)

SMS Volume

SMS Success
MoSMS, MtSMS – No SCCP cause, or has following causes:

MAP Error code

1 - Unknown Subscriber
5 - Unidentified Subscriber
6 - Absent Subscriber_SM
27 - Absent Subscriber
31 - Subscriber busy for MT SMS

TCAP Dialogue error

Application Context Name Not Supported

Call Minutes
Number of conversational minutes for Mo and Mt calls.

Affected Roamers by cell

The Affected roamers in % plotted on the map deep red = 100%
KPIs
This is a summary of all KPIs in the Outbound roaming portal:

Number of Attached Roamers

Number of Affected Roamers
Number of Successful SMS
Number of Mt Call Attempts
Data volume (MB)
Number of Active Roamers
Number of Users with Attach Failures
Number of Users with Data Setup Failures
Number of Users with Call Failures
Number of Users with SMS Failures
Attached failures split on 2G, 3G and 4G error causes and roaming network
Data setup failures split on 2G, 3G and 4G error causes and roaming network
SMS failures split on MAP error codes
SMS attempts split on Mt and Mo
Call failures split on RANAP/BSSMAP etc error codes
Lost cell (Last cell before cancel location)
Cells where roamers are located