Page 25 - Methodology for inter-operator and cross-border P2P money transfers

directly using the Scenario description field in the than required). However, it must be clearly empha-
TAL. In that case, it must be made sure that each sized that great care is strongly advised when creat-
description text is unique. Another way can be to ing and maintaining this list. Undetected errors can
use a generic Scenario descriptor (e.g., for a cate- cause artefacts and errors in later stages of process-
gory such as “Cross-border” and to construct the ing which are hard to detect. For instance, a typing
final scenario description use for aggregation from error in an IMEI may lead to “ignored” data items
respective fields of the TAL, e.g., from the Scenar- with respective consequences for completeness and
io, the FromConfigName, and the ToConfigName. correctness of results. The same goes for date and
• Date range information may be crucial for lat- time entries.
er allocation of data. Typically, JOIN statements The basic structure of the DAL mirrors a team, named
with corresponding ON conditions including time- after the DFS operator and the country it is testing.
range BETWEEN clauses will be used. Make sure This team uses a pair of devices according to the
that date/time ranges given in the TAL are consis- basic role assignment and set-up described in previ-
tent, either by using complete date/time informa- ous sections of this document. However, the structure
tion, or by using respective DATEADD statements. also provides for extensions of this basic scheme:
• Column names should be chosen to not contain
blank spaces or other non-alphanumerical charac- – A team may change the devices during the cam-
ters. This may ease data processing e.g., in SQL paign, or a re-installation of apps can lead to new
data bases. If desired, creation of “friendly text” ID’s being allocated.
for output can be done in respective SQL state- – Devices can assume different roles, e.g., devices
ments, e.g., replacing underscore (_) by blanks. can switch between the DFS and the Observer
role.
– Devices can be swapped between teams, or teams
11�7 Device Assignment List (DAL) can be allocated to different testing tasks (e.g., a
This list connects measurement data to teams. team testing operator A can start to test operator
In the following, we will assume that there are two B after some time).
ID’s:
The DAL has a column structure which is, for reading
• The MSW ID identifies data from the Multi-stop- convenience, shown there transposed with explana-
watch app. tions for each column.
• Data from network background measurement are As the content of a DAL is quite project-specific, no
identified by the IMEI of the device on which the templates are provided. It is however recommended
respective testing app is installed . to use the tables below for construction of respec-
4
tive files.
The DAL structure is chosen such that it is user-friend-
ly (in the sense that its structure is not more formal

Methodology for inter-operator and cross-border P2P money transfers 23