Real-Time System Data View

FUNCTION SPECIFICATION

71/155 17-CSA 121 01/15-V1 Uen A

Copyright

© Ericsson GmbH 2021. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Contents

Contents

1 Revision Information 1

2 Overview 3

3 Function 5
3.1 General 5
3.2 Real-Time SIs Polling and Reporting 5
3.3 Real-Time Graphical Representation 15
3.4 Operation and Maintenance 16

4 Operational Conditions 21
4.1 Operation and Maintenance Reference Information 21
4.2 Capabilities 22

Glossary 23

Reference List 25

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

Real-Time System Data View

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Revision Information

1 Revision Information

Changes in MSC-S 18.4

This document is based on Real-Time System Data View,
71/155 17-CSA 121 01/11-V1 Uen , Rev. A.

— Rev. A

• Editorial changes only.

Changes in MSC-S 18A

This document is based on Real-Time System Data View,
71/155 17-CSA 121 01/10-V1 Uen, Rev. C.

— Rev. A

Real-Time System Data View:

• Introduction of RTSDV Framework including following suites:

— RSV Suite: Migration of ‘‘Real-time System data View’’ tool to RSV

Suite.

— (Implemented using FFD): CDA Suite.

• RTSDV Framework, capability enhancement.

Changes in MSC-S 17A

Real-Time System Data View:

— Rev. C

• System Indicator SPU has been added.

— Rev. B

• Editorial changes only.

— Rev. A

• This is a new document.

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 1

 Real-Time System Data View

2 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Overview

2 Overview

The function ‘‘Real-Time System Data View’’ (RTSDV) provides the ability to
report a predefined set of System Indicators (SIs) in real-time. SIs are data
provided by real-time measurements of essential characteristics of a node
collected according to RTSDV Framework solution principles. RTSDV Framework
contains different suites used for the purposes of performance management.
These suites are running on a data server independently to collect and visualize
SIs obtained from network nodes in real-time. Either of RTSDV Framework suites
can be used or both of them.

The Real-time System View (RSV) Suite collects and visualizes SIs that can be
used to evaluate system stability and performance. It is possible to define upper
or lower thresholds, so that the user is alerted through RSV Suite when an SI
exceeds or recedes the critical levels.

The Call Drop Analyzer (CDA) Suite collects and visualizes SIs that can point to
abnormal call failures. Based on samples collected, CDA Suite provides real-time
indication about potential node or network issues.

Dependencies

— The execution environment of the RTSDV Framework must be a Linux®

based Data Server that supports secure connection (UDP over IPsec) to the
Router. The Data Server can be implemented also on Virtual Machine (VM) in
the cloud environment.

Figure 1 displays an example of the product configuration applicable for MSC-S.

Figure 1 Example of MSC-S Product Configuration

Note: Figure 1 is also applicable to TSC-S.

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 3

 Real-Time System Data View

Real-Time System Data View Documentation Overview

Table 1
Function Specifications Procedural Information
Real-Time System Data View Managing the Real-Time System Data
View
Real-Time System Data View, Activate
Real-Time System Data View,
Deactivate

For further information on the RSV Suite see the video in Figure 2.

Figure 2 Real-time System View Suite Video

4 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Function

3 Function

3.1 General
The ‘‘RTSDV’’ function is based on polling a CP and reporting predefined SIs to
the RTSDV Framework suite. The Suite requests SI data from the CP using a
proprietary protocol over UDP. The CP is configured to receive these requests
on a specific UDP socket and provides the values of the requested SIs in the
response. The SI data collected are used for the graphical representation of the
corresponding SI s in real-time.

3.2 Real-Time SIs Polling and Reporting

Each RTSDV Framework suites consists of a main engine and of one or many
clients. An instance of the suite main engine sends for each defined SI Set a
Real-Time System Data Request message to the defined target CP as shown in
Figure 1 in predefined intervals. The SI Set is a predefined list of SIs that can be
configured per suite of the RTSDV Framework. An SI Set or a combination of SI
Set can be defined per suite for polling, based on the node type that is interrogated
and the functionality of the suite.

At reception of a Real-Time System Data Response message from a CP, the

suite main engine executes the following actions:

— Extraction of the received time-stamped SI data

— Evaluation of the SI data

— Creation of events if required (RSV Suite only)

— Creation and update of the log files

— Provision of all necessary information for the client(s) to create and update
the Graphical User Interface (GUI)

For more information on the log files see Section 3.4.5 on page 19.

Client instance is used for graphical representation of data collected by main

engine.

When ‘‘RTSDV’’ function is not active Real-Time System Data Request messages
are discarded by the CP. During restart, no request reaches the CP, since the UDP
socket is closed and re-initiated.

3.2.1 RSV Suite

Following tables present the SI Sets to be used by RSV Suite.

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 5

 Real-Time System Data View

Table 2 SI Set call1

(1)
SI Name SI Abbreviation SI Description
EOS codes Eos Latest EOS codes
EOS codes to be shown
are selected out of a
predefined list.
IPU Load Load IPU average load for a 5
seconds period
Mobile Originating Calls Moc Traffic level counter for
mobile originating calls
Mobile Terminating Calls Mtc Traffic level counter for
mobile terminating calls
Number of Calls in Tpr Traffic level counter for
pre-alerting internal resources in
position pre-alerting
Pre-alerting indicate
that a call has seized
internal resources and
call setup is progressing
without knowing if it
will be successful or not.
SPU Load Spu SPU load in the last 100
ms interval in percent
Total Number of Calls Tar Traffic level counter for
resources in position
alerting or speech
(1) The SI abbreviation is used as title for each SI in the graphical representation.

Table 3 SI Set conv1

(1)
SI Name SI Abbreviation SI Description
EOS codes Eos Latest EOS codes
EOS codes to be shown
are selected out of a
predefined list.
IPU Load Load IPU average load for a
5 seconds period

6 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Function

(1)
SI Name SI Abbreviation SI Description
Number of Calls in Tpr Traffic level counter for
pre-alerting internal resources in
position pre-alerting
Pre-alerting indicates
that a call has seized
internal resources and
call setup is progressing
without knowing if it
will be successful or not.
Number of incoming SIP Sipi Traffic level counter for
calls incoming SIP calls
Number of outgoing SIP Sipo Traffic level counter for
calls outgoing SIP calls
SPU Load Spu SPU load in the last 100
ms interval in percent
Total Number of Calls Tar Traffic level counter for
resources in position
alerting or speech
(1) The SI abbreviation is used as title for each SI in the graphical representation.

Table 4 presents the SI Set that is recommended to be defined in RSV Suite based
on the node type that is polled.

Table 4 SI Set Recommendation

Node Type SI Set Recommendation
MSC-S call1
TSC-S conv1

3.2.2 CDA Suite

Following tables present the SI Sets to be used by CDA Suite.

Table 5 SI Set cdaset1

(1)
SI Name SI Abbreviation SI Description
Latest Cause Code gCau External Cause
collected on A-Interface Code that trigger
abnormal call release on
A-Interface
Message direction on gDir Message direction on
A-Interface A-Interface

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 7

 Real-Time System Data View

(1)
SI Name SI Abbreviation SI Description
Message initiated call gMsg Latest logged message
release on A-Interface that initiate abnormal
call release on
A-Interface
Global route number for gRop Global route number
A-Interface over which message is
received on A-Interface
Latest Cause Code uCau External Cause
collected on Iu-Interface Code that trigger
abnormal call release on
Iu-Iinterface
Message direction on uDir Message direction on
Iu-Interface Iu-Interface
Message initiated call uMsg Latest logged message
release on Iu-Iinterface that initiate abnormal
call release on
Iu-Interface
Global route number for uRop Global route number
Iu-Interface over which message is
received on Iu-Interface
EOS codes Eos Latest EOS codes
EOS codes to be shown
are selected out of a
predefined list.
(1) The SI abbreviation is used as title for each SI in the graphical representation.

Table 6 SI Set cdaset2

(1)
SI Name SI Abbreviation SI Description
Latest Cause Code sCau External Cause Code
collected on SIP/SIP-I that trigger abnormal
interface call release on SIP/SIP-I
interface
Message direction on sDir Message direction on
SIP/SIP-I interface SIP/SIP-I interface
Message initiated call sMsg Latest logged message
release on SIP/SIP-I that initiate abnormal
interface call release on SIP/SIP-I
interface
Global route number for sRop Global route number
SIP/SIP-I interface over which message is
received on SIP/SIP-I
interface

8 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Function

(1)
SI Name SI Abbreviation SI Description
Latest Cause Code lCau External Cause
collected on Sv-interface Code that trigger
abnormal call release on
Sv-interface
Message direction on lDir Message direction on
Sv-interface Sv-interface
Message initiated call lMsg Latest logged message
release on Sv-interface that initiate abnormal
call release on
Sv-interface
Host pointer for lRep Pointer to Host Data on
Sv-interface Sv-interface
(1) The SI abbreviation is used as title for each SI in the graphical representation.

Table 7 SI Set cdaset3

(1)
SI Name SI Abbreviation SI Description
Latest Cause Code ssCau External Cause Code
collected on SIP interface that trigger abnormal
call release on SIP
interface
Message direction on SIP ssDir Message direction on
interface SIP interface
Message initiated call ssMsg Latest logged message
release on SIP interface that initiate abnormal
call release on SIP
interface
Global route number for ssRop Global route number
SIP interface over which message
is received on SIP
interface
Latest Cause Code siCau External Cause Code
collected on SIP-I interface that trigger abnormal
call release on SIP-I
interface
Message direction on SIP-I siDir Message direction on
interface SIP-I interface

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 9

 Real-Time System Data View

(1)
SI Name SI Abbreviation SI Description
Message initiated call siMsg Latest logged message
release on SIP-I interface that initiate abnormal
call release on SIP-I
interface
Global route number for siRop Global route number
SIP-I interface over which message
is received on SIP-I
interface
(1) The SI abbreviation is used as title for each SI in the graphical representation.

Table 8 SI Set cdaset4

(1)
SI Name SI Abbreviation SI Description
EOS codes Eos Latest EOS codes
EOS codes to be shown
are selected out of a
predefined list.
Latest Cause Code collected ssCau External Cause Code
on SIP interface that trigger abnormal
call release on SIP
interface
Message direction on SIP ssDir Message direction on
interface SIP interface
Message initiated call ssMsg Latest logged message
release on SIP interface that initiate abnormal
call release on SIP
interface
Global route number for ssRop Global route number
SIP interface over which message
is received on SIP
interface
Latest cause code collected siCau External Cause Code
on SIP-I interface that trigger abnormal
call releasel on SIP-I
interface
Message direction on SIP-I siDir Message direction on
interface SIP-I interface

10 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Function

(1)
SI Name SI Abbreviation SI Description
Message initiated call siMsg Latest logged message
release on SIP-I interface that initiate abnormal
call release on SIP-
interface
Global route number for siRop Global route number
SIP-I interface over which message
is received on SIP-I
interface
(1) The SI abbreviation is used as title for each SI in the graphical representation.

Table 9 SI Set cdaset5

(1)
SI Name SI Abbreviation SI Description
Latest Cause Code lCau External Cause
collected on Sv-interface Code that trigger
abnormal call release on
Sv-interface
Message direction on lDir Message direction on
Sv-interface Sv-interface
Message initiated call lMsg Latest logged message
release on Sv-interface that initiate abnormal
call release on
Sv-interface
Host pointer for lRep Pointer to Host Data on
Sv-interface Sv-interface
EOS codes Eos Latest EOS codes
EOS codes to be shown
are selected out of a
predefined list.
(1) The SI abbreviation is used as title for each SI in the graphical representation.

Table 10 presents the SI Set that is recommended to be defined in CDA Suite

based on the node type that is polled.

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 11

 Real-Time System Data View

Table 10 SI Set recommendation

Node Type SI Set Recommendation
MSC-S cdaset1
cdaset1 and cdaset2
cdaset1 and cdaset3
(1)
cdaset3 and cdaset5
TSC-S cdaset4
(1) Recommended when SRVCC Relocation Scenario 2 always apply in the Network or the MSC-S
that is polled always implements SRVCC based on SRVCC Relocation Scenario 2. For more
information about Relocation Scenario 2 refer to FSs LTE to GSM Handover (SRVCC) and
LTE to WCDMA Handover (SRVCC)

Page 12 shows information about values of each SI

Table 11 SI values
(1)
SI Abbreviation Description SI values
gDir, uDir,sDir, ssDir, SIs representing 1 = Message coming to
siDir, lDir message direction MSC
2 = Message going from
MSC
gMsg Latest message initiated 1 = BSSMAP CLEAR
abnormal call release on COMMAND
A-interface
2 = BSSMAP CLEAR
REQUEST
(2)
5 = MO DTAP
DISCONNECT
(2)
6 = MO DTAP
RELEASE
7 = MT DTAP
DISCONNECT
8 = MT DTAP RELEASE
(2)
13 = MO DTAP
RELEASE COMPLETE
14 = MT DTAP RELEASE
COMPLETE
17 = DTAP CM SERVICE
REJECT

12 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Function

(1)
SI Abbreviation Description SI values
uMsg Latest message initiated 3 = RANAP RELEASE
abnormal call release on COMMAND
Iu-interface
4 = RANAP RELEASE
REQUEST
(2)
9 = MO RANAP/NAS
DISCONNECT
(2)
10 = MO RANAP/NAS
RELEASE
11 = MT RANAP/NAS
DISCONNECT
12 = MT RANAP/NAS
RELEASE
(2)
15 = MO RANAP/NAS
RELEASE COMPLETE
16 = MT RANAP/NAS
RELEASE COMPLETE
18 = RANAP/NAS CM
SERVICE REJECT
lMsg Latest message initiated 26 = PS TO CS
abnormal call release on RESPONSE
Sv-interface
27= PS TO CS COMPLET
E NOTIFICATION
29 = PS TO CS CANCEL
NOTIFICATION
sMsg, ssMsg, siMsg Latest message initiated 300-399 = REDIRECTIO
abnormal call release on N MESSAGES
SIP and SIP-I interface
400-499 = CLIENT
ERROR MESSAGES
500-599 = SERVER
ERROR MESSAGES
600-699 = GLOBAL
FAILURE MESSAGES
1004 = BYE
1005 = CANCEL

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 13

 Real-Time System Data View

(1)
SI Abbreviation Description SI values
gCau Latest Cause Code for For more information
A-Interface refer to FSA-Interface,
Section H: Base Station
System Management
Application Part,
BSSMAP Message
Formats and Coding
and FS A/Iu-Interface,
Section K: DTAP and
RANAP/NAS, Message
Formats and Coding for
Call Control and Call
Related Supplementary
Service Procedures
uCau Latest Cause Code for Iu For more information
- Interface refer to FS Iu-Interface,
Section H: Radio Access
Network Application
Part, RANAP, Message
Formats and Coding
and FS A/Iu-Interface,
Section K: DTAP and
RANAP/NAS, Message
Formats and Coding for
Call Control and Call
Related Supplementary
Service Procedures
sCau, ssCau, sICau Latest Cause Code for For more information
SIP and SIP-I interface refer to AI List of
Cause Code and
Location Information
Mappings
lCau Latest Cause Code for For more information
Sv-interface about IE Type "SRVCC
Cause" refer to FS
Sv-Interface, General
Aspects, Message
Formats and Coding
for SRVCC
(1) The SI abbreviation is used as title for each SI in the graphical representation.
(2) Under MO calls are also considered DRVCC calls and A/Iu-interface messages during and
after SRVCC procedure (For more information about SRVCC procedure refer to FSs LTE to GSM
Handover (SRVCC). LTE to WCDMA Handover (SRVCC) and PS to CS SRVCC for
Additional Call)

14 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Function

3.3 Real-Time Graphical Representation

The SI data collected from a CP through the main engine are used by the client to
produce the corresponding graphical representation.

The display center can be one of the following devices:

— The Data Server itself

— A remote desktop

— The OSS

The remote desktop or the OSS are acting as a thin client display center, just for
the remote graphical representation of the SI data provided by the Data Server
via SSH tunneling.

Optionally, if Gnuplot is installed on display center data collected by CDA suite can
be displayed in forms of charts.

It can be selected whether a single curve (‘‘Single Mode’’) or multiple curves

are displayed in a window of the GUI, where each curve represents one SI. In
case that multiple curves are displayed, representation of instant SI values
(‘‘Peak Mode’’) or average SI values (‘‘Mean Mode’’) can be additionally selected.
For more information on the graph modes, refer to User Guide Managing the
Real-Time System Data View.

Up to 2000 samples of each SI (if available) are saved in a ring buffer and are
used for the calculation of the average SI value for the graphical representation in
Mean Mode. The CP responses are correlated to the sent requests in a depth of
these 2000 past requests. Responses to older requests are discarded.

In case that a graphical representation of a specific SI is requested, the RTSDV

Framework suites provides an indication for the occurrence of the selected SI.

If response message is not received for a polling request message, this is visible in
the graphical representation as zero values. This also applies to the restart and to
any communication failure between the CP and the Data Server.

A possible clock adjustment in the CP is not visible in the presented graph. Time
differences in such cases are visible only through the timestamps of the logged
events.

RSV Suite uses different colors for the background of the displayed graph
depending on certain events:

— Red color in case that the instant SI value exceeds a predefined upper
threshold.

— Blue color in the following cases:

• The instant SI value recedes below a predefined lower threshold.

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 15

 Real-Time System Data View

• There is a communication failure between the CP and the Data Server.

— Black color in the following cases:

• The instant SI value is within the normal value range.

• The previously exceeded or receded instant SI value returns back to the

normal value range.

In case that an instant SI value exceeds or recedes a predefined upper or lower

threshold respectively (event), the RSV Suite produces an audible warning and
logs it in a dedicated log file by the first occurrence of the event, if these options
are activated.

RSV Suite represent these events in another tab of the main window including
the following data:

— Time and date of the event

— The event name

— The CP name

— The SI Set name

— The instant SI value

Only the last 86400 events, if available, can be displayed in the window.

3.4 Operation and Maintenance

3.4.1 Function Activation

The ‘‘RTSDV’’ function is activated by the AXE parameter SISFNC from the AXE
parameter set OMSRC. The administration of the function is performed as described
in Section 3.4.3 on page 17.

In order to be possible for node to provide SI values for the SIs requested by
RTSDV Framework Suites, the SIs must be activated through the proprietary
command RVSIS .

For more information refer to Operational Instruction Real-Time System Data

View, Activate.

3.4.2 Function Deactivation

‘‘RTSDV’’ function is deactivated by the AXE parameter SISFNC from the AXE
parameter set OMSRC. The administration of the function is performed as described
in Section 3.4.3 on page 17.

16 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Function

In order to be possible for node to not provide SI values for the SIs requested by
RTSDV Framework Suites, the SIs must be deactivated through the proprietary
command RVSIR.

For more information refer to Operational Instruction Real-Time System Data

View, Deactivate.

3.4.3 Function Administration

Administration in MSC-S
After the activation of the function in the CP, it is possible to create and
administer a socket by commands RVSOI and RVSOC. These commands enable the
communication between the CP and the Data Server. Once the socket is created,
the configured socket data can be verified through the answer printout REAL TIME
VIEW SOCKET DATA. In order the socket to become functional, it needs to be
deblocked by command RVSBE.

The following commands are part of the administration of the ‘‘RTSDV’’ function:

— Socket initiation through command RVSOI

— Socket removal through command RVSOE

— Change socket data through command RVSOC

— Print socket data through command RVSOP

— Reset socket's statistics data through command RVSOR

— Socket blocking through command RVSBI

— Socket deblocking through command RVSBE

The activation status of an SI can be verified through the answer printout REAL
TIME VIEW USER DATA by ordering the proprietary command RVSIP.

The default DSCP value for this function is CS2 (which equals to value 16). For
more information refer to User Guide Managing IP Integration.

Note: The function administration described in Section 3.4.3 on page 17 is also

applicable to the TSC-S.

Administration in Data Server

Starting the RSV Suite main engine is achieved by ordering command
startRsvtool. Starting the RSV GUI client is achieved by ordering command
startRsvGui.

Accordingly, CDA Suite main engine is started by ordering command

startCdatool. CDA GUI client is started by ordering command startCdaGui.

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 17

 Real-Time System Data View

Thenetwork configuration file of each RTSDV Framework suite contains the

connection and configuration data for all CPs .

The following mandatory CP-related information must be filled per SI Set:

— IP address

— Port Number

— System Release Name

— CP Name

— CPU Type

Additionally, the following optional information can be filled for every suite
configuration:

— Upper and lower thresholds per SI . (only applicable for RSV Suite)

— Logging of the instant SI values (deactivated by default).

— Real-Time System Data Request interval (default value is 250 ms).

— Coordinates (height and width) of the graphical representation window,

which define its size and position.

— Scaling values (vertical division or multiplication) of the graphical

representation window per SI Set.

In case that a graphical representation of EOS codes is also requested, the EOS
Codes configuration file can also be edited. One EOS code can be requested and
matched to a preselected set of EOS codes.

The following information can be filled in the network configuration file:

— Audio (deactivated by default).

— Logging of the events (activated by default).

EachRTSDV Framework suite provide the ability to back up it's configuration

by ordering command backupDirDB. Each time the command backupDirDB is
ordered, the compressed file toolDirDB_<day>_<month>_<year>_<time>.zip
is created containing a backup copy of the configuration files of the suite and is
stored in the suite's DB folder.

All running processes on the Data Server can be listed by ordering the command
listKill.

For more information, refer to User Guide Managing the Real-Time System Data
View.

18 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Function

3.4.4 Printing Socket Data

Command RVSOP is used for retrieving one or all sockets' data.

The answer printout REAL TIME VIEW SOCKET DATA includes the following data:

— Socket Identity

— Socket State

— Socket Blocking State

— Socket Administrative State

— Socket Fault Code

Additionally, the following socket data can also be printed in answer printout
REAL TIME VIEW SOCKET DATA depending on optional parameters given in
command RVSOP:

— Local Port Number

— Local IP address

— Base Local IP address

— Remote Port Number

— Remote IP address

— Number of messages per second

— Total number of messages

— Number of sent messages

— Number of received messages

3.4.5 SIs File Output

[Link] Output of SI values

The time-stamped instant SI values received with response for a corresponding

CP are stored in a log file and retained for a period of one week, if this option is
activated. The log file <name><cp>_<day> is created for the response messages
during a day of a week.

In case no response is received, then the log file is not updated. This also applies to
the restart and to any communication failure between the CP and the Data Server.

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 19

 Real-Time System Data View

[Link] Output of SI values in events

In case that an instant SI value of a CP exceeds or recedes a predefined upper

or lower threshold respectively (event), it is possible to log it in a dedicated log
file, if this option is activated. The log file is updated only the first time that the
event occurs. When the value returns inside the normal range, then the log file
is updated accordingly.

The following log files are created:

— netRsvEvLog_<day> includes the events produced during a day of a week.

— [Link] automatic archive file includes the network event log files
of the week.

The log files can be retained for a period of one week.

20 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Operational Conditions

4 Operational Conditions

4.1 Operation and Maintenance Reference Information

Input Elements

Table 12
Commands in MSC-S
RVSOI
RVSOE
RVSOC
RVSOP
RVSOR
RVSBI
RVSBE

Table 13
RSV suite commands in Data Server
startRsvtool
startRsvGui
listKill
backupDirDB
rsvShowThr

Table 14
CDA suite commands in Data Server
startCdatool
startCdaGui
listKill
backupDirDB
cdaEos
cdaCause
cdaShowLog
cdaShowRep
cdaStatNetwork

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 21

 Real-Time System Data View

CDA suite commands in Data Server

cdaStatNodes
cdaShowThr

Table 15
AXE Parameters
SISFNC

Output Elements

Table 16
Printouts
REAL TIME VIEW SOCKET DATA Answer Printout

4.2 Capabilities
Capabilities for each RTSDV Framework suite:

— One command can be executed at a time (see Table 12).

— One dedicated UDP socket can be defined.

— The received instant SI values as well as the instant SI values in case of an

event are stored and retained in the Data Server for a period of one week.

— A history of the last 2000 samples (if available) per SI are used to calculate
the average SI value for the graphical representation in Mean Mode.

— The interval between the polling request messages has a lower limit of 10
ms and an upper limit of 86400 sec.

Note: It is not recommended to choose polling intervals smaller than 20 ms

and larger than 1 sec (default value 250ms).

— Each Suite can support up to 40 Nodes.

— Only the last 86400 events, if available, can be displayed in the window.

22 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Glossary

Glossary

AXE OSS
Public Telephone Exchange System Operations Support System

BSSMAP PS
Base Station System Management Application Packet switched
Part
RANAP
CDA Radio Access Network Application Part
Call Drop Analyzer
RSV
CP Real-time System View
Central Processor
RTSDV
CS Real-Time System Data View
Circuit switched
SI
DRVCC System Indicator
Dual Radio Voice Call Continuity
SIP
DSCP Session Initiation Protocol
Differentiated Services Code Point
SPU
DTAP Signal Processor Unit
Direct Transfer Application Part
SRVCC
EOS Single Radio Voice Call Continuity
End Of Selection
SSH
GUI Secure Shell
Graphical User Interface
TSC-S
IP Transit Switching Center Server
Internet Protocol
VM
IPU Virtual Machine
Instruction Processor Unit
UDP
MO User Datagram Protocol
Mobile Originating

MT
Mobile Terminating

MSC-S
MSC Server

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 23

 Real-Time System Data View

24 71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25

 Reference List

Reference List

[1] A/Iu-Interface, Section K: DTAP and RANAP/NAS, Message Formats and

Coding for Call Control and Call Related Supplementary Service Procedures
FUNCTION SPECIFICATION

[2] A-Interface, Section H: Base Station System Management Application Part,

BSSMAP Message Formats and Coding
FUNCTION SPECIFICATION

[3] Iu-Interface, Section H: Radio Access Network Application Part, RANAP,

Message Formats and Coding
FUNCTION SPECIFICATION

[4] List of Cause Code and Location Information Mappings

APPLICATION INFORMATION

[5] LTE to GSM Handover (SRVCC)

FUNCTION SPECIFICATION

[6] LTE to WCDMA Handover (SRVCC)

FUNCTION SPECIFICATION

[7] Managing IP Integration

USER GUIDE

[8] Managing the Real-Time System Data View

USER GUIDE

[9] PS to CS SRVCC for Additional Call

FUNCTION SPECIFICATION

[10] Real-Time System Data View, Activate

OPERATIONAL INSTRUCTION

[11] Real-Time System Data View, Deactivate

OPERATIONAL INSTRUCTION

[12] Sv-Interface, General Aspects, Message Formats and Coding for SRVCC
FUNCTION SPECIFICATION

71/155 17-CSA 121 01/15-V1 Uen A | 2021-01-25 25