You are on page 1of 11

LOGOS for Ericsson 3G

1
4/27/16
Confidential

Nokia 2014

Whats new
Thanks to the OSSii agreement its now possible to understand the raw data file
format(L3 messages) from Ericsson and Huawei RNCs and LTE eNBs.
Due to the requests to expand our business in MV environment we worked on
Logos tool and provided the same functionality as for NOKIA with Ericsson 3G.
The services which will benefit from such functionality are:

Smartphone Optimization
Application Impact Management
Network Optimization and Assurance
Multilayer Optimization(we can trace Nokia LTE over E// 3G)

2
4/27/16
Confidential

Nokia 2014 - Secret until Launch - Nokia Launch Planning Template

Post Processing(Logos for UE profiling & NW Optimization)


DASHBOARD ASSESSMENT

High level review of key performance metrics for the entire network or customized aggregation.
PERFORMANCE
Network Access Performance
PRACH access distance
PRACH access quality
RRC and RAB Connection setup
Drop Call Analysis
RRC and RAB clear codes
RF link characteristics
Service Quality
Voice vs. Data performance
Handover
Inter-RAT activity

3
4/27/16
Confidential

PROFILING
End User Performance
Per user system usage(VIP)
Identify problematic users
Assess impact of roamers
Fast trains and high mobility
M2M
UE Profiling
Device based reporting
Brand, Model, Type
(Smartphone, Tablet, Dongle or
Handset)
Marketing insights
Device penetration
Usage characteristics

Nokia 2014 - Secret until Launch - Nokia Launch Planning Template

CAPACITY
Traffic Modeling
Call Type analysis
Throughput by data type
Call / session duration
Smartphones capacity impact
RRC states
Signalling load
Fast dormancy

ROAMERS
Network Affinity
Review of distribution of roamers
Home network
Performance of roaming
subscribers
UE profile of roamers
Impact on network resources

Application Impact Management


Scope: OTT Instant Messaging Apps for a Tier1 operator
Cell State Change

Spender potential

Discover Higher Spender


potential

Instant Messaging
signalling
detailed analysis

Improvements action
defined

1
Radio Capacity

Identification of average
retransmission per
Application
Correlation with RF and
UEs

2
OTT background

Enhancing Radio Capacity


Planning adding
Application impact

How OTT background


service are keeping busy
the Network

4
4/27/16
Confidential

Retransmissions

DNS Load

IP sessions

Load split among DNSs


is not balanced/
optimized

Growing number of IP
sessions caused by
Application Impact on
FW, DPI, NAT

APN Traffic

Entertainment

Protocols split

Where and how Users


are enjoying
entertainment offering

Statistics

Access

IT, Big IP

Marketing

Strategy

Nokia 2014 - Secret until Launch - Nokia Launch Planning Template

Fast Users Impact


Device Penetration
& usage
. Applications Vs
Devices

10

Data Capturing

Ericsson 3G Network with the availability of GPEH data collector


WRAN features Flexible ROP for GPEH (OSS feature) and GPEH Capacity
Increased - Reduced ROP Periodicity (RNC feature) must be both set to
ACTIVATED and run in parallel to provide higher level of event intensity and
recording capability of the GPEH events.
Support up to GPEH W14A
Possibility to fetch the data for one day(24 hours or if not possible for 12hours)

5
4/27/16
Confidential

Nokia 2014 - Secret until Launch - Nokia Launch Planning Template

How to perform data acquisition


Data acquisition must be done following the rules described in the link below:
https://confluence.int.net.nokia.com/display/NPOGLS/Ericsson+GPEH+acquisition
Launch the OSS Network Explorer GUI and on the Performance menu of the Network
Explorer window, click Initiate data Collection then click RAN Measurements
In Data collection subscription profiles, add Subscription Profile of type GPEH. Select
RNC/eNB to be configured. Make note of the RNC/eNB software version (useful for
determining the GPEH version)
Select access cells. It is recommended to include all cells served by the RNC/eNB.
Select set of GPEH events to be recorded. For the List of 3G Events for GPEH collection
must be cross referenced to ensure all needed messages are collected.
Set gpehDataLevel = ALL_DATA, means the entire message is recorded in ASN.1 format
with IMEI decoding. The SGSN parameter Iu_IdentityImeiEnabled shall be set to true (the
default
is false)
otherwise
RANAP
signaling
contains no IMEI information.
6
4/27/16
Nokia 2014
- Secret until Launch
- Nokia Launch
Planning Template
Confidential

How to perform data acquisition

Launch the OSS Network Explorer GUI and on the Performance menu
of the Network Explorer window, click Initiate data Collection then click
RAN Measurements
7
4/27/16
Confidential

Nokia 2014 - Secret until Launch - Nokia Launch Planning Template

How to perform data acquisition

Make sure to select all data!


8
4/27/16
Confidential

Nokia 2014 - Secret until Launch - Nokia Launch Planning Template

How to perform data acquisition


Set UE Fraction. (range 0-1000) where 1000 equates to 100% or all UE collected. This
should be set to 1000
Create a scheduled profile (if none exists), select the desired start and end times. Then
press finish to complete the process.
NOTE:
A duration of 15 minutes (one ROP) must be selected.
The default file size in 15 MB this is too small!
It is recommended to increase the ROP file size limit setting to at least 25
MB.
Maximum RNC storage is 100MB Hence maximum recommended file size is
50MB.
Check again that the correct List of 3G Events for GPEH collection has been set!
The subscription profile must be resumed at least 3 minutes before any ROP you
wish to collect data for.
To verify the profile has not been suspended (inactive "OpState", check the mail
"Data Collection Subscription Profiles - Main GUI"

9
4/27/16
Confidential

Nokia 2014 - Secret until Launch - Nokia Launch Planning Template

List of messages that must be collected


INTERNAL events:
INTERNAL_CHANNEL_SWITCHING
INTERNAL_OUT_HARD_HANDOVER_SUCCESS
INTERNAL_PACKET_DEDICATED_THROUGHPUT
INTERNAL_RAB_ESTABLISHMENT
INTERNAL_RAB_RELEASE

NBAP events:
NBAP_RADIO_LINK_RECONFIGURATION_FAILURE
NBAP_RADIO_LINK_RECONFIGURATION_PREPARE
NBAP_RADIO_LINK_RECONFIGURATION_READY
NBAP_RADIO_LINK_SETUP_REQUEST

RRC events:
RRC_CELL_UPDATE_CONFIRM
RRC_PHYSICAL_CHANNEL_RECONFIGURATION
RRC_RADIO_BEARER_RECONFIGURATION
RRC_RADIO_BEARER_RECONFIGURATION_COMPLETE
RRC_RADIO_BEARER_RECONFIGURATION_FAILURE
RRC_RADIO_BEARER_RELEASE
RRC_RADIO_BEARER_SETUP
RRC_RADIO_BEARER_SETUP_COMPLETE
RRC_RRC_CONNECTION_RELEASE_COMPLETE
RRC_RRC_CONNECTION_REQUEST
RRC_RRC_CONNECTION_SETUP
RRC_RRC_CONNECTION_SETUP_COMPLETE
RRC_RRC_MEASUREMENT_REPORT
RRC_TRANSPORT_CHANNEL_RECONFIGURATION

RANAP events:
RANAP_COMMON_ID
RANAP_DIRECT_TRANSFER
RANAP_INITIAL_UE_MESSAGE
RANAP_IU_RELEASE_COMMAND
RANAP_IU_RELEASE_COMPLETE
RANAP_IU_RELEASE_REQUEST
RANAP_RAB_ASSIGNMENT_REQUEST
RANAP_RAB_ASSIGNMENT_RESPONSE

10
4/27/16
Confidential

RANAP_RAB_RELEASE_REQUEST

Nokia 2014 - Secret until Launch - Nokia Launch Planning Template

How to perform data acquisition


Output directory:
Data is located in a subdirectory corresponding to the NE Context of the RNC. For
example:
/var/opt/ericsson/nms_umts_pms_seg/segment1/SubNetwork=RNC1/MeContext=RNC1
GPEH files will be made available in 15 mins intervals. These need to retrieved / FTPed
to our system for parsing. Otherwise after a configurable time files are deleted
automatically to conserve OSS file system space.
Make sure to get the binary files format! They always end with _MPx_bin where x is
a integer number
Last things to note:
GPEH events recorded by the RNC are always timestamped to network time. (We
assume this to be UTC)

11
4/27/16
Confidential

Nokia 2014 - Secret until Launch - Nokia Launch Planning Template