Page 36 - Methodology for measurement of Quality of Service (QoS) Key Performance Performance Indicators (KPIs) for Digital Financial Services

ANNEX E

Naming rules, data structures and related processes used in the pilot
project

E.1 NAMING TABLE E-1: Data base format definition for team/
device assignment list
E.1.1 General
Element names shown in bold face are functional names ELEMENT TYPE
which shall be used consistently throughout all relevant Team ID Varchar(128)
documents. They may also have abbreviations used for Device ID Varchar(64)
brevity but only in the current clause of this document.
Start time and date of assignment datetime
E.1.2 Teams End time and date of assignment datetime
Each team shall be given a unique Team ID (TID), made
of alphanumeric characters. The TN can be freely cho- The end time can be NULL indicating that the assign-
sen but it shall not be changed over time. ment is ongoing.

E.1.3 Devices E.3 NOTIFICATION SMS
The Device ID (DID) is composed of the device’s role
and index (e.g. SP1, FP2, and OP), underscore (‘_’) and E.3.1 Transfer and data handling process
the last 6 digits of the device’s IMEI. The Notification SMS (NSMS) (sent to the A and B par-
On log sheets, an abbreviated name using only the ty) contain information about the DFS transaction. This
device’s role is used. The full DID can be looked up by information is used to complement the overall informa-
the respective entry in the device/team assignment tion.
data (see below). The steps of this process are:
The IMEI is the identifier displayed if the code *#06# • NSMS arrive at respective devices
is entered in the Phone Dial window. • The SMS backup process (see SMS Backup & restore
In case of dual-SIM devices, they may have 2 IMEI. In
that case, the IMEI for the first SIM position is used for app) sends, when invoked, an e-mail with an XML
file attachment to a specific location. This XML file
the DID. Usually this is the first IMEI displayed for *#06# contains a copy of all SMS which were stored on the
(to be verified). device at the time of invocation.
Example for a full DID: SP1_123456
On log sheets, Device Role Aliases can be used in- • The attachment is processed by importing it into the
stead of the short role names. The following aliases are project data base.
defined: The NSMS do not contain information about the devic-
SP Full Capability es involved. This information must therefore be added
during the overall process of NSMS collection.
FP Low Capability
This is done using the following definition and pro-
cess:
E.2 TEAM/DEVICE ASSIGNMENT LIST
• The set-up of SMS backup allows to configure the
A list is kept which records the assignment of devices Subject. This Subject shall contain the DID of the re-
to teams. As this assignment may change over time, the spective device.
respective time window is also recorded. • For import, the DID shall be added to the respective
The list has the following elements:
data items.
• As each backup file is a snapshot of all SMS on the
device, subsequent executions will produce dupli-
cates of NSMS. The data structure/import process
must have provisions to handle these duplicates.

34 • Methodology for measurement of Quality of Service (QoS) Key Performance Indicators (KPIs) for Digital Financial Services