<<

Performance of International Location Update in and networks

Contact Information:

Sanaz Moshirian Author(s): Sanaz Moshirian E-mail: [email protected] E-mail: [email protected]

External advisor(s): Anders Högsell Hi3G Access AB Address: Lindhagensgatan 98, 112 51 Stockholm, Sweden Phone: +46735333333

University advisor(s): Dr.Patrik Arlos Department of Communication systems

Internet : www.bth.se School of Computing Faculty of Computing Phone : +46 455 38 50 00 Blekinge Institute of Technology Blekinge Institute of Technology : +46 455 38 50 57 371 79 Karlskrona Sweden Faculty ABSTRACT

Since Mobile network operator (MNO) relies on many Business Support Systems (BSS) and Operation Support Systems (OSS) it should be assured that operator’s systems supports the requirements of the future.

This thesis shall focus on the “start-to-end” aspects that must be considered to ensure that International Roaming continues to operate flawless. The thesis experience Long Term Evolution (LTE) in case of international roaming by measuring the end to end location update delay.

In order to evaluate the LTE performance of international roaming, the delay time has been measured by the means of tracing tools for several different international roamers and the results has been compared with the results achieved for local user. The outcome has been compared with the respecting results in 3G network the statistical results has been provided and the graphs has been plotted to study the performance.

Based on the results obtain on this thesis, it has been concluded that local user acts more stable to get attach to the network, i.e. there are less fluctuation in delay times for local user. Also the delay time in 3G networks is more than the LTE networks, however 3G networks acts more stable and there are less fluctuation to get connects to 3G networks.

Keywords: International Roaming, LTE, Delay, Tracing, Performance.

CONTENTS

Contents ABSTRACT ...... I CONTENTS ...... II LIST OF FIGURES ...... IV LIST OF TABLES ...... VI ACRONYMS ...... VII 1 INTRODUCTION ...... 1

1.1 INTRODUCTION ...... 1 1.2 RELATED WORKS ...... 1 1.3 AIMS AND OBJECTIVES ...... 1 1.4 RESEARCH QUESTIONS ...... 2 1.5 EXPECTED OUTCOMES...... 2 1.6 RESEARCH METHODOLOGY ...... 2 1.7 RISKS ...... 3 1.8 MOTIVATION ...... 3 2 BACKGROUND ...... 4

2.1 PROTOCOLS...... 4 2.1.1 SS7 protocol ...... 4 2.1.2 Diameter ...... 5 2.2 LTE NETWORK ARCHITECTURE ...... 6 2.2.1 Overview ...... 6 2.2.2 LTE nodes and interfaces ...... 7 2.3 DIAMETER NODES ...... 10 2.3.1 Diameter Client and Server ...... 10 2.3.2 Diameter Relay Agent ...... 11 2.3.3 Diameter Proxy Agent ...... 12 2.3.4 Diameter Redirect Agent ...... 12 2.3.5 Diameter Translate Agent ...... 13 3 METHODOLOGY ...... 14

3.1 INTERNATIONAL ROAMING ...... 14 3.2 IMPLEMENTATION ...... 14 4 ANALYSIS AND RESULTS...... 19

4.1 TEST SET UP AND ANALYSES ...... 19 4.1.1 Setup and Analyses for international roamer on LTE network ...... 19 4.1.2 Set Up and Analyses for international roamer on 3G network ...... 23 4.1.3 Set up and Analyses for Local user attaching LTE & 3G network ...... 26 4.2 COMPARISON OF ATTACH LATENCY FOR LOCAL USERS AND INTERNATIONAL ROAMERS IN LTE NETWORK ...... 29 4.2.1 Delay difference for international users and local user ...... 29 4.2.2 How is the LU latency differs between international operators ...... 30 4.3 COMPARISON OF ATTACH LATENCY IN LTE AND 3G NETWORKS ...... 32 4.3.1 Comparison of LU latency for each of the operators in 4G and 3G ...... 32 4.3.2 Total comparison of attach latency in 3G and 4G networks ...... 35 5 CONCLUSION AND FUTURE WORK ...... 39

ii 5.1 CONCLUSION ...... 39 5.2 FUTURE WORK ...... 40 BIBLIOGRAPHY ...... 41 APPENDIX.1 ...... 43 APPENDIX.2 ...... 64

iii LIST OF FIGURES

Figure 2-1, Signaling Architecture [10] ...... 4 Figure 2-2, EPS network Architecture [15]...... 7 Figure 2-3, UMTS and EPS core network [16] ...... 7 Figure 2-4, EPS nodes and interfaces [16] ...... 8 Figure 2-5, Tracking area updates [16] ...... 9 Figure 2-6, LTE interworking with other 3GPP networks [16] ...... 9 Figure 2-7, PCRF role in LTE network [18] ...... 10 Figure 2-8, , Re-authentication and Session Termination [13] ...... 11 Figure 2-9, The role of Diameter Relay Agent (DRA) in optimizing the network [16] ...... 12 Figure 2-10, Diameter Proxy Agent [19] ...... 12 Figure 2-11, Diameter Redirect Agent Function [19] ...... 13 Figure 2-12, Diameter Translate Agent (TLS) Function [12] ...... 13 Figure 3-1, Sample scenario for interaction between MME and HSS in international roaming [16]...... 15 Figure 3-2, Simple message exchange between VPLMN & HMPLN [23] ...... 15 Figure 3-3, International roaming interfaces and international roaming brokers with DEA [7] ...... 16 Figure 3-4, International roaming interfaces and international roaming brokers without DEA [7]...... 17 Figure 3-5, Home routed architecture of subscribers’ traffic [16] ...... 17 Figure 3-6, LTE attach procedure in international roaming [25]...... 18 Figure 4-1, LU trace for UAE user roams under 4G network ...... 20 Figure 4-2, LU Delay time for UAE user roams under LTE network ...... 21 Figure 4-3, LU Delay time for UAE user in LTE network between 13:00 and 16:00 ...... 21 Figure 4-4, LU Delay time for user roams under Sweden LTE network ...... 22 Figure 4-5, LU Delay time for Slovenia user roams under Sweden LTE network...... 22 Figure 4-6, LU Delay time for Norway user roams under LTE network ...... 23 Figure 4-7, LU trace for UAE user roams under 3G network ...... 24 Figure 4-8, LU Delay time for UAE user roams under 3G network ...... 25 Figure 4-9, LU Delay time for Austria user roams under 3G network ...... 26 Figure 4-10, LU Delay time for Slovenia user roams under 3G network ...... 26 Figure 4-11, LU Delay time for Norway user roams under 3G network ...... 26 Figure 4-12, LU Delay time for local user roams under LTE network ...... 27 Figure 4-13, LU Delay time for local user roams under LTE network ...... 28 Figure 4-14, LU Delay time for local user roams under 3G network ...... 28 Figure 4-15, Comparison of LU latency for local user and sample operator’s user roams under LTE network ...... 29 Figure 4-16, Comparison of LU latency for local user and sample operator’s user roams under LTE network on sample time stamps ...... 30 Figure 4-17, Comparison of attaching latency for sample operators roam on 3G and LTE network on sample times ...... 31 Figure 4-18, LU trace for Slovenia user roams under 4G network ...... 32 Figure 4-19, Comparison of LU Delay time for UAE user roams under 3G and LTE network ...... 33 Figure 4-20, Comparison of LU Delay time for Austria user roams under 3G and LTE networks ...... 33 Figure 4-21, Comparison of LU Delay time for Slovenia user roams under 3G and LTE networks ...... 34 Figure 4-22, Comparison of LU Delay time for Norway user roams under 3G and LTE networks ...... 34

iv Figure 4-23, Comparison of LU Delay time for Local user roams under 3G and LTE networks ...... 35 Figure 4-24, Comparison of attaching latency for sample operators roam under 3G and LTE network ...... 36 Figure 4-25, Comparison of LU latency for sample operators roams on 3G and LTE network on sample times ...... 37

v LIST OF TABLES

Table 1, Diameter base protocol commands [13] ...... 5 Table 2, Sample LU test results for UAE user in 4G network on 21 August 2015 ...... 19 Table 3, Sample LU test results for UAE user in 3G network on 21 August 2015 ...... 23 Table 4, LU test results with Local SIM Card in 4G network on 27th of August ...... 26 Table 5, Min, Average, Standard Deviation and Max delay in 4G network ...... 29 Table 6, Min, Average, Standard Deviation and Max delay in 4G network ...... 35 Table 7, Routing availabilities on 3G & 4G networks ...... 37 Table 8, LU test results with UAE SIM Card in 4G network ...... 43 Table 9, LU test results with UAE SIM Card in 3G network ...... 45 Table 10, LU test results with Austria SIM Card in 4G network ...... 46 Table 11, LU test result with Austria SIM Card in 3G network ...... 49 Table 12, LU test results with Slovenia SIM Card in 4G network ...... 51 Table 13, LU test results with Slovenia SIM Card in 3G network ...... 53 Table 14, LU test results with Norway SIM Card in 4G network ...... 55 Table 15, LU test results with Norway SIM Card in 3G network ...... 57 Table 16, LU test results with Local SIM Card in 4G network ...... 59 Table 17, LU test results with Local SIM Card in 3G network ...... 61

vi ACRONYMS

3G 3rd Generation 3GPP 3rd Generation Partnership Project 4G 4th Generation AF Application Function AVP Attribute-Value Pairs BSS Business Support Systems CN Core Network CSFB Circuited Switch Fall Back DRA Diameter Relay Agent DEA Diameter Edge Agent eNodeB Evolved -B EPS Evolved Packet System E-UTRAN Evolved Universal Terrestrial Access Network GPRS General Packet Radio Services GRX GPRS Roaming Exchange GSM Global System for Mobile Communications GGSN Gateway GPRS Support Node GTP GPRS Tunneling protocol HPLMN Home PLMN HSS Home Subscriber Server IETF Engineering Task Force IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IP Internet Protocol IPX Internetwork Packet Exchange LTE Long Term Evolution MME Entity MSC Mobile Switching Center MNO Mobile Network Operator OSS Operation Support Systems PCEF Policy Enforcement Features PCRF Policy charging and rules function PDN Packet Data Network PGW Packet Gateway PLMN public land mobile network PSTN Public Switched Telephone Network QCI QoS class identifier QoS Quality of Service RAN Radio Access Network SAE System Architecture Evolution SCP Signaling Control Point SGSN Serving GPRS Support Node SGW Service Gateway SS7 Signaling System 7 SSP Signaling Switching Point STP Signaling Transfer Point TCAP Transaction Capabilities Application Part TCP Transmission Control Protocol UE User Equipment UMTS Universal Mobile System UTRAN Universal Terrestrial Radio Access Network

vii VPLMN Visited VPLMN VoIP Voice over IP

viii 1 INTRODUCTION 1.1 Introduction

In recent years the growth of could be observed in providing fast speed data and video telephony, also to provide the better quality voice, more coverage and more capacity to be able to meet the user demands and requirements.

Long Term Evolution (LTE) initiated by Third Generation Partnership Project (3GPP) [1] and has been developed and considered for providing the high bitrates and low latency with the objective of 150Mbps data rate. LTE has been standardized in the 3GPP, release 8. LTE also has a simplified architecture as it is all IP network, unlike the other generations of network which they needed a circuited switched core.

Some other features of LTE networks is capability of end to end Quality of Service (QoS) and route optimization which makes operators more interested to implement LTE networks. LTE networks have been also developed to support seamless connection which provides QoS in the entire network.

International Roaming is one of the common services which have been provided by operators to the customers to be able to use their local SIM cards around the world; the users can continue to use the voice and data service while traveling to different countries. Recently operators start to offer LTE roaming as the new service, which supports faster and better quality of data service.

In this thesis our aim is to focus location update for a local user in a specific LTE network and in case of international users, roam in that specific LTE network, also to verify the how it is differ for the same users performing location update in LTE network and in 3G network. 1.2 Related Works

In [2] the authors studied Roaming Authentication in 3G network and tried with different authentication methods. Paper [3] worked on call arrival rate and other policies for different subscriber to check the performance. In paper [4] the authors investigate the characteristic of authentication traffic in LTE networks. Paper [5] describe the interworking between TCAP and Diameter and analyze some specific scenario such as GSM or 3G subscribers roam in LTE networks. All above papers provides how authentication works as a part of location update and in paper [5] it is possible to get an overview of roaming. In this paper we will have more depth view of location update by not only checking on the authentication but also other process that is needed for a mobile to get attach to a network as part of the work. For other parts of the work different comparison will be study. 1.3 Aims and objectives

The purpose of this thesis is to show the quality of international roaming in case of using LTE network, by assessing the latency and investigation of solution to measure the latency. This project will evaluate the latency in LTE network in case of international roaming which affects the customer experiences. Location update latency is the time which takes for a user to get attach to a network, i.e. the time from when user’s phones try to get connected to network until it gets attach to network. In this thesis we measure this delay to verify how this

1 delay differs for international users and local users also how it differs in case of attaching to LTE networks in compare with 3G networks.

Also the objectives are to measure this latency and experience different scenarios which might affect the delay time of the location update. Comparing the location update latency when the home users, using the LTE network or when the international users using the same LTE network i.e. international roaming and comparison of Location Update latency when international users, roam in LTE network & in 3G network. 1.4 Research questions

1. How can the location update latency be evaluated for international roamer in LTE networks?

2. To which extent the delay differs for an international roamer from the delay for a Local user to get connected to network in LTE Networks?

3. How the latency in LTE networks is different from 3G networks with respect to international roaming Location Update?

1.5 Expected outcomes

This thesis provides a clear picture about how to measure the latency along with sketch and graphs showing the location update latency by collecting sample location update data for different users of different operators, also some comparison will be done to achieve the Statistics for different user location update correlated with time delay and authentication delay in case of using national and international LTE networks and in case of using 3G and LTE networks. 1.6 Research Methodology

This thesis is based on experimental and statistical data which has been collected on 3G and 4G networks within a Swedish Mobile Network Operator. Some sample operators would be chosen and implemented for LTE roaming both at the operators sides and the Internetwork Packet Exchange (IPX) providers side; the IPX provider act as a hub to route LTE data towards other operators along with providing the security and end to end quality of service, etc [6]; selected operators can use the same IPX provider or two different IPX providers, in case of using two different IPX providers the providers should be peered towards each other.

The selected operators will send sample SIM cards which will be used for international LTE Roaming tests. The received SIM cards will be configured and activated for LTE Roaming to be able to perform a successful LTE Roaming Location Update. By using a tracing tool the authentication time can be measured and location update latency would be evaluated, the achieved result will be discussed. Also the same experience will be done for 3G networks to compare the result with respecting test in LTE network.

As to answer RQ1, we will study the selected mobile operators for this thesis, by collecting the location update time with help of tracing tool. Once we identified an answer to RQ1, it would be possible to perform comparison for the achieved data for international operators and the local operator which leads us to answer the RQ2. To handle R3 we compare the results in 4G and 3G networks. This thesis will provide different test scenario and collaborate with GRX/IPX provider to handle the LTE roaming, with making sure that all LTE nodes such as MME (Mobility

2 Management Entity), PCRF (Policy charging and rules function) and HSS (Home Subscriber Server) working properly in case of roaming [7] [8]. This project will more focus on LTE data international roaming and performance analysis by evaluation of latency.

The reason we have selected this methodology is because LTE roaming is still new and there might be a need of improvement in LTE networks, by using the user experience and statistics the problems and improvements in the network can be shown and it can helps to improve the LTE network in some cases. 1.7 Risks

There might be user error with time stamping or tool problem such as tracing tool shows strange behavior, so the backup tracing tool should be considered to avoid this problem. But we are trying to test with samples in different times and days and trying to avoid these affect as much as possible to get the best answer. Some other risks might be switching to 3G when we don’t want or the SIMs is not compatible for the setting. Also some tools like steering system might affect the latency; tracing tool is a tool which is uses in international roaming cases to force the operators to attach to certain operator which might cause more delay for attaching to other operators, for this test the SIM cards has been excluded from steering tools to avoid external delay.

1.8 Motivation

This thesis focus on performance in LTE networks with regards to location update time delay in case of international LTE roaming. Understanding the quality of the network and user experience will lead to improved network performance and quality.

3 2 BACKGROUND 2.1 Protocols

Signaling System 7 (SS7) was one of the most important protocol in GSM and 3G networks for voice and SMS traffic but in the new generation of mobile networks (LTE network), SS7 protocol become less and less important. Nowadays by using full LTE network where IP Multimedia System (IMS) is developed to carry the voice and SMS traffic over IP, SS7 protocol has been replaced by new protocol such as Diameter and Session Initiation (SIP) Protocol.

Still so many operators didn’t implement full LTE network and they use Circuited Switch Fall Back (CSFB) to switch back to 3G when it come to voice traffic.

2.1.1 SS7 protocol

SS7 protocol supports out of band signaling in routing, billing establishment of the call and exchanging the information.

“Signaling provides exchanging information between the call elements” and out of band signaling refers to signaling that has separate channel for signaling information and does not use the same path as conversation. SS7 provides over 56 or 64 Kbps data speed and allows signaling during the entire conversation [9] [10].

SS7 provides 3 kind of signaling points, these signaling points describes bellow. Signal Switching Point (SSP), which is a telephone switch that originates, terminates, and switches the calls. Signal Transfer Point (STP), which is a packet switch that receives and routes the network traffic between signaling points. Signaling Control Point (SCP), which is a database that helps to determine the needed information regarding the routings and other necessary information [10]. Figure (1) shows a simple signaling architecture.

Network1 Network 2

SCP SCP

SCP SCP STP STP

SSP STP STP

SSP

SSP

SSP

Figure 2-1, Signaling Architecture [10]

4 2.1.2 Diameter

Diameter Protocol has developed by Internet Engineering Task Force (IETF) as a replacement for RADIUS, Kerberos, TACACS+, for providing Authentication, Authorization and Accounting (AAA).

Authentication shows if the user or device who is requesting to access the network is the correct user or device that has clams to be and it consist of three parts which is user authenticating, message authenticating and device authenticating. Re-authentication might happen if the session get expire or new authentication request receive from the server [11].

Authorization is the procedure which defines if the user actually allowed to access to the part of the network that requested [11].

Accounting is the procedure of defining to which part of the network user had access and to which extend for the purpose of billing and cost checking [11].

Diameter protocol builds on application layer and is supports by Transmission Control Protocol and Stream Control Transmission Protocol (SCTP), so the reliable transport would be provided also it controls the and avoid any congestion on the link. Diameter has some other feature, diameter is peer to peer instead of Client-Server and any node can initiate to send a request and the ability of peer discovery and capability negotiation and exchange has been provided. Diameter supports end to end security but it is not mandatory, for securing the connection in diameter networks Transport Layer Security (TLS) or Internet Protocol Security (IPSec) can be used [11] [12].

Diameter base commands have been defined for handling different type of diameter . Table (1) lists some of the diameter base protocol commands [13].

Table 1, Diameter base protocol commands [13] Command name Abbreviation Abort-Session-Request ASR Abort-Session-Answer ASA Accounting-Request ACR Accounting-Answer ACA Capabilities-Exchange-Request CER Capabilities-Exchange-Answer CEA Device-Watchdog-Request DWR Device-Watchdog-Answer DWA Disconnect-Peer-Request DPR Disconnect-Peer-Answer DRA Re-Auth-Request RAR Re-Auth-Answer RAA Session-Termination-Request STR Session-Termination-Answer STA

For example Capability Exchange is one the diameter base protocol commands and is the first command that will be exchanged, so the CER command will be send and CEA command will be received which the result code would be shown in the CEA command [13].

::= < Diameter Header: 257, REQ > { Origin-Host } { Origin-Realm }

5 { Host-IP-Address } { Vendor-Id } { Product-Name } [ Origin-State-Id [ Supported-Vendor-Id ] [ Auth-Application-Id ] [ Inband-Security-Id ] [ Acct-Application-Id ] [ Vendor-Specific-Application-Id ] [ Firmware-Revision ] [ AVP ]

::= < Diameter Header: 257 > { Result-Code } { Origin-Host } { Origin-Realm } { Host-IP-Address } { Vendor-Id } { Product-Name } [ Origin-State-Id ] [ Error-Message ] [ Failed-AVP ] [ Supported-Vendor-Id ] [ Auth-Application-Id ] [ Inband-Security-Id ] [ Acct-Application-Id ] [ Vendor-Specific-Application-Id ] [ Firmware-Revision ] [ AVP ]

Result code AVP can have different value. It might show some information (1xxx), the successful transaction (2xxx), protocol errors (3xxx), Transient Failures (4xxx) and Permanent Failures (5xxx) [13].

2.2 LTE network architecture

2.2.1 Overview

At the same time with development of the LTE network in 2004, 3rd Generation Partnership Project (3GPP) core network architecture has been changed. The evolution of changing GPRS (General Packet Radio Service) network is called System Architecture Evolution (SAE) which has more simplified architecture as it is an all IP network. The core component of SAE is called Evolved Packet Core (EPC) and the combination of LTE and EPC is called Evolved Packet System (EPS) [14].

An EPS network support QoS in the whole network is also provides connectivity to Voice over IP (VoIP) and PDN networks. In order to provide QoS multiple bearers can be establish for different connection, i.e. the user can have a VoIP call at the same time with web browsing and the two bearers which assigned to VoIP and web browsing session provides the best QoS individually. Figure (2.2) shows a general architectural of EPC nodes and interfaces [15].

6

Figure 2-2, EPS network Architecture [15].

Compare to UMTS core network many nodes has been changed in evolve packet core but in radio access network it only simplified to evolved NodeB (eNodeB). eNodeB is the replacement of the previous NodeB and Controller (RNC) together. Also The UMTS Terrestrial Radio Access Network (UTRAN) is called evolved UTRAN (eUTRAN). Figure (2.3) shows the difference between UMTS and EPS core network at a high level [16].

Figure 2-3, UMTS and EPS core network [16]

2.2.2 LTE nodes and interfaces

At high Level LTE network can be divided to three groups of LTE access and transport network (eUTRAN), evolved packet core which is consists of logical nodes and applications. Figure (2.4) shows these three groups along with nodes and interfaces [16].

7

Figure 2-4, EPS nodes and interfaces [16]

LTE radio access network (eUTRAN) consists of eNodeBs which handle the entire radio management function and they can handle several calls at the same time. eNodeBs are connected to each other via X2 interface which make it possible for them to communicate to each other it results to cells not attach to the same eNodeB and makes an efficient radio management. The protocol between eNodeB and UE is called AS protocol. One of the major tasks of the eUTRAN is the management of radio resources by dynamic resource allocation to users and controlling the radio bearer, admission and mobility. It also provides security by performing the encryption when data is being transferred. The other task of the eUTRAN is header compression to avoid presenting a big amount of overhead and providing an efficient use of radio interfaces. In the end it can be considered that eUTRAN provides a signaling connectivity and bearer towards the MME and SGW [15] [16].

Home Subscriber Server (HSS) is a database that contains all users’ information such as where the subscriber is located or to which Packet Data Network (PDN) is connected. HSS also performs the authentication and authorization of the users and has the ability to apply the restriction on the subscription on necessary time. HSS has the function of controlling and managing the calls and sessions [16] [17].

Mobility management Entity (MME) provides the signaling between the User Equipment (UE) and core network, Non (NAS) protocols is the protocols used between UE and core network which is terminates at MME. MME defines and allocates the temporary identity to the UEs, and check the authorization of UEs, in total all the eNodeBs are managed by MME. To located the idle user when it is necessary MME supports Tracking area and it supports paging to find the specific UE which is shown in Figure (2.5). Some other features of the MME are roaming and handover. Basically MME has three major functions; bearer management that is establishing, terminating and maintenance of the bearers. Connection management that is establishing a secure connection by initiation a ciphering and integrating a protection algorithm and the last function is location management which includes tracking area update to make the network ready for any possible incoming session. Besides these three functions MME is also responsible for providing the control plane function to support the interaction between the /3Gs network and LTE network that is shown if Figure (2.6) [15] [16] [18].

8

Figure 2-5, Tracking area updates [16]

Serving Gateway (SGW) has the primary function of handling the data plane; all subscribers’ packet data will pass through the SGW and has the function of the mobility management and anchoring of the user plane during the handover between the eNodeBs. SGW connected with S1-U interface to eNodeB and send or receive the packet data and transmit the packet data toward PDN gateway via S5 or S8 gateway, also mobility management between the LTE network and other 3GPP networks such as 2G/3G networks this can be achieve by using the S4 interface which shows in Figure (2.6). MME controls the SGW via S11 interface [16] [18].

Figure 2-6, LTE interworking with other 3GPP networks [16]

Packet Data Network Gateway (PGW) acts as an exiling point for packet data interface and transmit the traffic towards external PDNs as well as the entry point of the traffics from other PDNs, it acts as the mobility anchor for the interaction between the 3GPP networks and non 3GPP networks as shown in Figure (2.6). Any users can connect to several PGWs simultaneously to be able to access different PDNs. PGW also the firewall functionality as well as packet filtering functionality, it can also allocate IP addressed to the users and the ability to supports Policy Enforcement Features (PCEF) to apply the charging and other defined rules by operators with regards to usage and resource allocation [16] [18].

9 Policy and Charging Rule Function (PCRF), is responsible for controlling and deciding the policies and flow based charging on the network, it also has control over the PCEF that is part of PGW and send the decided charging rule to PCEF for applying the charging functionality. QoS class identifier (QCI) and bit rates is being provided with PCRF function to define the data flow according to the users’ subscription and enforce it to PCEF to being applied on the users. By this means PCRF provides the QoS authorization and helps to apply both online and offline charging. Figure (2.7), shows the PCRF role. Application Function (AF) in the picture refers to network node with an application which needs policy and charging control [15] [18].

Figure 2-7, PCRF role in LTE network [18]

Several interfaces used between the nodes in LTE network to help routing the traffic in beneficial way. S1-MME is the interface between the eNodeB and MME to send the signaling. S1-U is used between the eNodeB and SGW to define the user plane. Between the MMEs S10 interface is being used in case of any changes at MME side. X2 is the interface that has been provides between eNodeBs to make handover possible and avoid any packet loss. To make it possible for MME to have control over the bearer establishment and path switching, S11 interface is being used between the MME and SGW and PGW and is base on GPRS Tunneling Protocol Version 2 (GTPv2). By using S6a interface, MME can get the subscriber information from HSS and perform the Authentication, Authorization and Accounting (AAA interface). S5 is the signaling interface between the serving gateways or between the SGW and PGW to establish bearer in case of any changes on SGW side, in roaming cases S8 interface will replace the S5 interface. Gx is the interface between to PCRF and PGW to send the policy enforcement to PCEF which is located in PGW and also retrieve the data flow for applying the QoS. Rx is the interface between the Application Function (AF) and PCRF to send the policy to PCRF, in IP Multimedia Subsystem (IMS), AF role is done by Proxy Call Session Control Function (P-CSCF). SGi is the interface that connects PGW to external PDN networks and is based on IP address with the possibility to exchange signaling as well [16].

2.3 Diameter Nodes

2.3.1 Diameter Client and Server

As it discussed before authentication and authorization of the subscribers based on the user profile is part of the diameter function, the node in diameter that has this responsibility is

10 called server. Basically diameter is based on the client – Server architecture with has the peer to peer structure. Diameter client is placed on the edge of the network and receives all requests from the users and generate the AAA message, in fact diameter client is Network Access Server (NAS), this result that diameter server node can have the server functionality on some cases and client functionality on some other situation and can provide session management, routing management and client management some other functionalities of diameter server are performing loop detection and determining duplicate messages, maintain the stateful or stateless authentication state machines which can be stateful/stateless client or stateful/stateless server, also stateful or stateless accounting state machines which can be client or stateful/stateless server. Stateful or stateless session can be establish based on the requirement from the application, in case the session needs to be maintain for specific duration. Diameter server can perform the re-authentication, re-authorization or aborting the session if requires for example in prepaid service, it might be necessary to perform re- authentication, so that diameter server makes sure that the user is still using the service. In the end diameter server has the functionality of terminating the session for example in case of session time out or client restart. Diameter servers communicate the timeout AVP to define the expiration of the session. Authentication, re-authentication and termination of the session between the client and diameter server are shown in Figure (2.8) [13] [19] [20] [21].

Figure 2-8, Authentication, Re-authentication and Session Termination [13]

2.3.2 Diameter Relay Agent

Diameter Relay Agent (DRA), forward the connection or association request messages to other diameter nodes based on diameter realm, host and application. DRA will never perform the AAA and never change the content of the messages, the only modification that DRA does is inserting or removing the routing data (Route Record AVP).DRA use the realm routing table to find the routing path, realm routing tables contains supporting realms, known peers and AVPs, DRA also performs the loop detection on the receiving message however it does not keep track of sessions [19] [21].

11 By using DRA it is possible to optimize the LTE network. Since fully meshed diameter network is quite complex to administrate or configure, DRA can play a similar role to STP in SS7 network by linking all the diameter nodes forward the requests and answers between them. DRA can provides scalability and simplify configuration by connecting and routing between nodes of the same network or different network. This has been shown in Figure (2.9) [16] [6].

Figure 2-9, The role of Diameter Relay Agent (DRA) in optimizing the network [16]

2.3.3 Diameter Proxy Agent

Diameter Proxy Agent, has the similar role as DRA and it forwards the request messages according to realm table with one difference, diameter proxy has the ability to modify the message content, thus it has the ability of enforcing the policy and defining the policies, validating the receiving AAA requests and originate the AAA reject messages to the client if necessary. Diameter Agent should keep the track of all NAR resources and limiting the usage resources on necessary cases. Diameter proxy agent in roaming scenarios can provide the topology hiding function. Figure (2.10) shows the diameter proxy agent function [19] [21].

Figure 2-10, Diameter Proxy Agent [19]

2.3.4 Diameter Redirect Agent

12 Diameter Redirect Agent, has only one function of returning the routing information which is necessary for other diameter nodes, it does not originate any message or change the AVP. Upon receiving any request message from one diameter node, diameter redirect agent performs a look up in its database and back the answer message with redirect information to the node that made the request, after that diameter redirect agent gets disconnect from the loop, by that other nodes does not require to maintain the routing table locally and simplify their function. Figure (2.11) shows diameter redirect agent function [19].

Figure 2-11, Diameter Redirect Agent Function [19]

2.3.5 Diameter Translate Agent

Diameter Translate Agent, are diameter proxies that act as a translator between different nodes and translate between different protocols. For example they provide translation between diameter and RADIUS or between diameter and (MAP) as it shown in Figure (2.12). Diameter translate agent can maintain stateful session or transaction states for authorized sessions [19] [21].

Figure 2-12, Diameter Translate Agent (TLS) Function [12]

13 3 METHODOLOGY

3.1 International Roaming

LTE is also like GSM network, a Public Land Mobile Network (PLMN), which provides communication for mobile to mobile and mobile to fix network. The PLMN area has restriction and generally it restricted to one country, but in some cases one country provides network extension in some other countries. There might be an overlap on PLMN area of different countries in border areas [22].

Roaming is a function that provides by the network operators and allows the user of a certain network to use the network of another operator based on the wholesale agreement between the two operators [7]. A PLMN calls Home PLMN (HPLMN), when subscriber located at home network and when that subscriber roams, it would be called Visited PLMN (VPLMN) [22]. 3.2 Implementation

In LTE networks in case of international roaming scenario when subscriber “A”, from HPLM roams to VPLMN, there will be a need to perform some configuration at Mobility Management Entity (MME); has the same role as SGSN and MSC in 3G networks; and Home Subscriber Server (HSS); has the same role as HLR in 3G networks; side to allow the subscriber use the VPLMN network. Bellow an example for a sample scenario in case of LTE roaming is explained.

When subscriber “A”, attempts to connect to VPLMN, the MME of the visited network can achieve the IMSI of the subscriber and from the IMSI it can drives the home domain. For example if the IMSI is equal to 20402xxxxxxxxxx then the realm would be epc.mnc002.mcc204.3gppnetwork.org. Then MME will perform a look up on its routing table to find the destination and send a diameter authentication (S6) towards the diameter relay/proxy of the HPLMN, since there would be a SCTP link available (it should be implemented when roaming agreement is established). Visited MME provides Home relay/proxy agent, the original host, original and destination realm AVPs. The relay agent of the home network will analyze this and from its routing tables find the next agent that is responsible to process this request in the home network; the next agent which would be responsible is the HSS in the home network, so the proxy agent adds the destination host to the diameter request, coming from visited network MME and forwards it to the HSS. HSS will send back then answer on the same route that request came [7]. In the end PCRF of the home country and visited country will communicate to exchange the QoS and charging control information which will be done trough S9 interface [16]. Figure (3.1), shows a sample scenario for interaction between MME and HSS in international roaming.

14

Figure 3-1, Sample scenario for interaction between MME and HSS in international roaming [16]

The simple message exchange between home network and visited network is shown in Figure (3.2)

Figure 3-2, Simple message exchange between VPLMN & HMPLN [23]

Since it would not be easy to establish a direct SCTP connection with hundreds of operators around the world separately, there would be a need of International roaming brokers (GRX/IPX providers). In this case the operator simply establishes one SCTP connection towards the agent of the roaming broker and from there it is possible to connect to all other roaming operators or other operator’s IPX providers [22]. In case of selected Sweden operator, Comfone [24] has been used as an IPX provider. The connection towards IPX provider is shown in Figure (3.3).

15

Figure 3-3, International roaming interfaces and international roaming brokers with DEA [7]

Figure (3.3) shows how a normal operator should get connected to the IPX provider. The black lines shows the interface between HSS/MME and IPS provider which is S6 interface and yellow lines shows the interface between PCRF and IPG provider which is S9 interface. Roaming interface shows with the red line. The operators can get connected to the IPX provider via their diameter Edge (proxy) agent (DEA), DEA makes for operators the possibility to hide their and IPX provider acts as diameter relay agent and provides the routing towards other operators, if other operators has other IPX provider it would be possible to make connection between the two IPX providers (make peering between to IPX provider) which is shown via purple line in the Figure (3.3).

If the roaming operator does not have any DEA agent it would be possible to make connection to the IPX provider directly by connecting the MME, HSS and PCRF towards the IPX agent which is shown in Figure (3.4)

16 Figure 3-4, International roaming interfaces and international roaming brokers without DEA [7]

Home routing is similar way to the way of transferring data traffic in 3G networks nowadays and the traffic is routes via GRX/IPX providers from the home PLMN towards the visited PLMN. This would be possible with S6 and S9 interface as discussed before and S8 interface which is providing the connection between visited network SGW and home network PGW. Home routing way of traffic is shown in Figure (3.5) [16].

Figure 3-5, Home routed architecture of subscribers’ traffic [16]

After all the installation and configuration has been done then it is time to perform the LTE attach on the VPLMN network. The procedure is described in Figure (3.6). To capture all data the tracing too will be used (OSIX tracing tools has been used on this thesis), a tracing tool is consist of a router which has been installed on the way of the LTE nodes like MME and all the message that will pass the network will be copied and save on one computer. By using one application it will be possible to get access to the captured data.

17

Figure 3-6, LTE attach procedure in international roaming [25]

Four different operators which are UAE, H3G Austria, Telecom Slovenia and Norway have been selected and configure on Hi3G Sweden Network for the test on this thesis, also a SIM Card from Hi3G Sweden has been used as a local SIM Card. The reason for selecting these operators is because of the limitation on the LTE roaming since LTE roaming is still new and still not so many operators are ready for LTE roaming, also they have different IPX and the peering between the IPX are not ready yet, so these are the four fist operators that were ready for LTE roaming test on Hi3G Sweden network.

In this research the time between the attach request sends by UE and the time that attach get completed has been used as the delay time.

18 4 ANALYSIS AND RESULTS

4.1 Test Set Up and Analyses

4.1.1 Setup and Analyses for international roamer on LTE network

Four operators have been selected on this thesis. The operators are located in Norway, Slovenia, Austria and United Arab Emirates (UAE). Location Update (LU) scenario has been performed with the SIM cards belongs to the mentioned operators by trying to register to LTE network on different hours and different days. The delay times have been recorded each time the LU scenario has performed. This has been achieved by using the tracing tool. Tracing tool is a router which is connected to all the nodes of the network and collects every message that passes between the nodes and writes a copy of it on one computer. In this thesis Osix application [26] has been used as the tracing tool application, Since Osix tracing tools has already been installed on the Hi3G network and it could capture all the messages that enter or leave the network. Osix is not an open source tracing tool but compare to some open source tracing tools it is more user friendly and provides so many options for filtering the messages. For this thesis the filtering has been done on the IMSI level, so only the message related to the required user has been captured. By using Osix it would be possible to trace the data from eNodeB till inside the network till IPX provider which it mean that the message has been left the network, also the filtering feature is provided to match the user requirement, for example it is possible to filter on IMSI, A number, B number, IP addresses, etc. it also makes it possible to select on which protocol the data need to be collected for instance diameter, SCCP, S1AP, GTP, etc, The data can be store up to two weeks and then it would be deleted to have capacity for saving other messaged in future. LU tests have been done on isolated laboratory environment the reason for this is that the signals from other operators do not interfere with the test and the phone does not try to connect to other operators in Sweden. Otherwise there will be no difference between testing in the laboratory or other places. The similar tests with all four operators have been done in 3G network as well and the data has been collected. Since there is national roaming provided in Sweden, it is not possible to get any data related to national roaming for comparison, instead the LU tests has been done with local SIM card connected to local 4G network and the data has been collected. To understand how the setup has been done, the UAE operator will be selected as an example and the data collection, traces and results will be explained. Table 2, shows examples data that has been collected for UAE user under 4G network. More samples for UAE operator has been provided in appendix.1, also the results related to other operators and local SIM have been shown in the appendix.1.

Table 2, Sample LU test results for UAE user in 4G network on 21 August 2015 LU time with UAE SIM in 4G network Sample Number Attach Request Attach Completed Delay in ms 1 09:39:03.192 09:39:04.923 1731 2 09:56:10.663 09:56:12.083 1420 3 10:01:42.732 10:01:44.225 1493 4 10:14:34.904 10:14:36.463 1559 5 13:12:27.033 13:12:28.149 1116 6 17:26:05.595 17:26:06.950 1355 7 13:46:43.194 13:46:44.291 1097

19 8 14:05:56.144 14:05:57.338 1194 9 14:24:50.914 14:24:52.076 1162 10 14:51:55.625 14:51:56.733 1108

Location update test has been done under 4G network and the sending and receiving messages has been recorded, using a tracing tool, which is shown in Figure (4.1). Since LTE network architecture is simpler than 3G network architecture and MME has both responsibility of SGSN and MSC, there would be less process for attaching to 4G network. In 4G case, first attach request will be received by MME from eNodeB, after that MME will perform authentication with UAE operator and send security mode command towards eNodeB. MME will send the create session message towards SGW, by that MME initiates to establish a default route and asks SGW to create a GTP tunnel (GPRS Tunneling Protocol), also MME sends LU request towards MSC (Since there is no IMS system in selected Sweden operator, Circuit Switched Fall Back (CSFB) method is being used for voice calls). By receiving the LU accept message from MSC, MME will send the attach acceptance message towards eNodeB. In the end eNodeB will send back UE capability information and attach complete message towards MME.

Figure 4-1, LU trace for UAE user roams under 4G network

By collecting the time of starting attach to the network and time of attach completing; it is possible to measure the delay time. The location update delay time has been shown in millisecond on the above tables. These results help us to have a better look in LU delay for international users in 4G networks in compare with 3G networks, also the difference of latency for international users to get connected to 4G network in compare with the local users. Figure (4.2) shows location update delay time for UAE user which has roamed under Sweden LTE network. The x-axis shows the number of tries. The received message will show as green when it sent or received successfully and after a wile will be change to back

20 color, if there is any error on sending and receiving message, it will show as red and the system might try several times to resend the message.

Figure 4-2, LU Delay time for UAE user roams under LTE network

Figure (4.2) show the delay for a 100 samples, i.e. 100 times of location update try for a UAE user who is roaming on Sweden networks. The minimum delay equals to 1081 milliseconds while the maximum delay is 2274 ms which shows a wide fluctuation in delay time on different hours or day. Standard deviation [27] of 170 that shows the delay time varies a lot depending on the time and date or some other elements in the network. Figure (4.3) shows the delay for UAE user between 13:00 PM and 16:00 PM to see if the delay is changing on different time of the day. As it shown in the Figure (4.3), the delay is almost 1100 ms between 13:00 PM and 15:00 PM and after that it raises again at about 16:00 PM. The attaching time is base on the Swedish time zone for all the figures (GMT+1).

Figure 4-3, LU Delay time for UAE user in LTE network between 13:00 and 16:00

21 By using the collected information which is provided in appendix.1, the same test has been done with some other operators in Austria, Slovenia and Norway in both 3G and 4G networks. Figure (4.4) shows location update delay time for Austria user which has roamed under Sweden LTE network, Figure (4.5) shows LU delay time for Slovenia user, roamed under Sweden LTE network and Figure (4.6) shows LU latency for Norway user that has roamed under Sweden LTE network. In all figures x-axis shows the number of tries.

Figure 4-4, LU Delay time for Austria user roams under Sweden LTE network

Figure 4-5, LU Delay time for Slovenia user roams under Sweden LTE network

22

Figure 4-6, LU Delay time for Norway user roams under LTE network

In all the above cases wide fluctuation for the attach latency can be observed.

4.1.2 Set Up and Analyses for international roamer on 3G network

Table 3 shows the example of collected data for UAE user on 3G network. More samples for UAE operator has been provided in appendix.1, also the results related to other operators and local SIM have been shown in the appendix.1.

Table 3, Sample LU test results for UAE user in 3G network on 21 August 2015 LU time with UAE SIM in 3G network Sample Number Attach Request Attach Completed Delay in ms 1 09:32:28.404 09:32:30.564 2160 2 09:47:11.600 09:47:14.300 2700 3 09:55:36.730 09:55:38.789 2059 4 10:01:41.857 10:01:43.915 2058 5 10:13:28.545 10:13:30.674 2129 6 10:23:18.623 10:23:20.683 2060 7 15:41:36.213 15:41:38.381 2168 8 16:00:26.468 16:00:28.508 2040 9 16:30:52.709 14:30:54.760 2051 10 16:46:37.684 16:46:39.796 2112

For a sample test that has been done with UAE test SIMs under 3G network, the sending and receiving messages has been captured by the tracing tool which is shown in figure (4.7).

23

Figure 4-7, LU trace for UAE user roams under 3G network

In this test, first location update request will be received by Mobile Switching Center (MSC) from Radio control Center (RNC) and MSC will request authentication, then attach request will be send towards SGSN from RNC. MSC will perform the authentication with the UAE operator and send security mode command towards RNC in order to perform ciphering of the messages, by receiving the security mode complete message, MSC will send the LU accept message towards RNC, after that and SGSN will perform the authentication with MSC and send security mode command towards RNC, by receiving security mode complete message, SGSN will send the attach accept message towards RNC. In the end RNC will send back attach complete message towards SGSN and location update will be done successfully.

Location update delay time for UAE user roaming under Sweden 3G network is plotted in Figure (4.8). Attach request time and attached complete time has been recorded in order to measure the delay.

24

Figure 4-8, LU Delay time for UAE user roams under 3G network

The fluctuation of the attaching time for UAE user roams under Sweden 3G network is much less comparing to LTE network. The minimum delay equals to 1968 ms and the maximum delay is 2700 milliseconds. The average LU latency is about 2102 ms with the standard deviation of approximately 112 which is less than the tests under LTE network.

According to these result the attaching time is more stable in 3G network than in LTE network, while it is much faster to get connected to LTE network. The average LU delay time in LTE network (1342 ms) in compare with 3G network (2102 ms) shows that the delay time to attach to 3G network for UAE user is almost double than the time to get connected to the LTE network.

The same test has been done for Austria, Slovenia and Norway operators under Sweden 3G network. Figure (4.9) shows location update delay time for Austria user that is roaming under Sweden 3G network, Figure (4.10) shows the LU latency for Slovenia user, under Sweden 3G network and Figure (4.11) shows LU delay time for Norway, roamed under Sweden 3G network.

25 Figure 4-9, LU Delay time for Austria user roams under 3G network

Figure 4-10, LU Delay time for Slovenia user roams under 3G network

Figure 4-11, LU Delay time for Norway user roams under 3G network

4.1.3 Set up and Analyses for Local user attaching LTE & 3G network

Table 4 shows the example of collected data for local user trying to attach LTE. More samples for local user attaching the LTE network and also attaching 3G network has been provided in appendix.1

Table 4, LU test results with Local SIM Card in 4G network on 27th of August LU time with Local SIM in 4G network

26 Delay in Sample Number Attach Request Attach Complete ms 1 09:39:58.948 09:39:59.605 657 2 09:47:53.319 09:47:54.170 851 3 09:53:14.270 09:53:14.968 698 4 10:02:19.836 10:02:20.667 831 5 10:10:16.764 10:10:17.723 959 6 13:55:53.024 13:55:53.995 971 7 13:59:45.525 13:59:46.448 923 8 14:06:56.126 14:06:57.020 894 9 14:12:42.994 14:12.44.146 1152 10 17:23:27.494 17:23:28.113 619

To find out more about the LU delay time for local user a sample location update test has been done and the messages has been captured by a tracing tool which is shown if figure (4.12)

Figure 4-12, LU Delay time for local user roams under LTE network

In this case like the international roamer case, the attach request will be send from eNodeB towards MME, then identify request message and authentication message will be communicated with eNodeB. MME will request SGW to create a session an activate the GRP tunnel, like it was discussed for UAE case, however there is one more step for local user in the process which is PGW will send an access request message towards PCRF to be able to apply the charging and policy rules and providing the quality of service, also PCRF

27 will keep the records of the usage of the user along with what services has been provided to be able to provide the charging information as soon as the PCRF accept the access, the session creation respond will be send from SGW. Then the location update message will be communicated between the MME and MSC and MME will send attach accept message towards eNodeB. In the end the UE capability information message will communicated between eNodeB and MME and the attached complete message will be sent towards MME.

Now it would be interesting to see how will the local Sweden SIM card behaves to get attach to LTE network in compare with the international roamers. It would be expected that the attach latency is much less, since the message will not get out of the network to reach the gateway. Figure (4.13), shows the attach latency results for a sample local user, that is trying to attach to the LTE network.

Figure 4-13, LU Delay time for local user roams under LTE network

By using the collected attaching time (it is provided in appendix.1), it is possible to plot the delay time for the local user under the 3G network that is shown in Figure (4.14).

Figure 4-14, LU Delay time for local user roams under 3G network

28

4.2 Comparison of attach latency for Local users and International Roamers in LTE network

4.2.1 Delay difference for international users and local user

The results that have been achieved for a local user has been compared with the results for the international roamers that have been attempting to attach to Sweden LTE network, this comparison has been shown in Figure (4.15).

Figure 4-15, Comparison of LU latency for local user and sample operator’s user roams under LTE network

For the mentioned sample operators, minimum delay, maximum delay, average delay and standard deviation has been calculated and listed in table 5 [27].

Table 5, Min, Average, Standard Deviation and Max delay in 4G network UAE 4G Austria Slovenia 4G Norway 4G Sweden (Local) 4G Delay 4G Delay Delay Delay Delay

Minimum 1081 647 1003 681 611

Mean 1342 870 1268 952 869

Standard 170 153 162 170 114 Deviation

Maximum 2274 1718 1863 1540 1189

To have a better look, the comparison has been done on sample times and the LU latency has been recorded which is shown in Figure (4.16).

29 2000 1800 1600 1400

1200 Local SIM 4G LU delay (ms) 1000 UAE 4G LU delay (ms) Delay 800 600 Austria 4G LU delay (ms) 400 Slovenia 4G LU delay (ms) 200 0 Norway 4G LU delay (ms)

09:33 09:56 10:21 10:45 11:13 13:17 13:55 14:20 14:48 15:38 16:08 16:25 17:43 18:03 Attach Time

Figure 4-16, Comparison of LU latency for local user and sample operator’s user roams under LTE network on sample time stamps

Figure (4.16) shows UAE user, Austria user, Slovenia user, Norway user who is roaming in Sweden plus Swedish user, all the users connected to Swedish 4G network and the attaching time is based on the Swedish time zone (GMT+1).

Although LU latency on some specific times such as 09:33 is less that LU latency of the international roamers, but still the average attaching time delay has no significant difference with Austria operator the reason is according to figure (4.12) there are more steps to perform LU for a local user such as getting access to the PCRF which cause more delay for a local user to get attach to the network. However a local user attaching time behavior is much stable than the other operators’ user which why the standard deviation less for local user compare to international users, since the message will not leave the local network to reach by destination (in case of the international roamers the message will be forwarded towards the IPX provider to get routed toward their PGW).

Standard deviation for a local user is less than international users, but there is not so much difference in average LU delay.

4.2.2 How is the LU latency differs between international operators

With Regards to section 4.2.1 LU latency is more stable for Local operator in compare with international users and standard deviation is less for the attaching time latency in case of locale user in compare to international users. This is not only the case according to Figure (4.16) the delay time varies for different international users as well, which cause the delay time for Austria user much less than USE user, one of the important reason is that the UAE node is much far away in compare with Austria node. To have a better vision on this comparison, Figure (4.17) has been plotted to show the comparison of the LU delay only for the four operators on Sweden LTE network on some specific times

30

Figure 4-17, Comparison of attaching latency for sample operators roam on 3G and LTE network on sample times

According to the graph it is shown that Slovenian user face more delay to attach to the network compare to Norwegian and Austrian user which is due to different configuration. The trace for trying to attach to 4G network for the Slovenian user has been plotted in Figure (4.18) and it is shown that diameter location update message (interface S6a) has been requested for this operator and identity request message has been sent towards eNodeB as well for understanding some parameter such as IMSI , IMEI, etc.

31

Figure 4-18, LU trace for Slovenia user roams under 4G network

More discussion about this LU latency for different international operators and local operator is provided in section 4.3.

4.3 Comparison of attach latency in LTE and 3G networks

4.3.1 Comparison of LU latency for each of the operators in 4G and 3G

To be able to understand the latency difference in 3G and 4G networks, it is required first to see how does every individual operator differ in 4G and 3G network then we can have a overview of attach latency difference for all operators. Figure (4.19) shows the comparison of LU delay time for UAE user under Sweden 3G and LTE networks on some sample times. Figure (4.20) compares the LU attach latency for Austria users under Sweden 3G and 4G networks. The same comparison has been done for Slovenia user which is shown on Figure (4.21), the comparison result for Norway user provided in Figure (4.22) and the comparison result for Norway user provided in Figure (4.23).

32

Figure 4-19, Comparison of LU Delay time for UAE user roams under 3G and LTE network

Figure 4-20, Comparison of LU Delay time for Austria user roams under 3G and LTE networks

33

Figure 4-21, Comparison of LU Delay time for Slovenia user roams under 3G and LTE networks

Figure 4-22, Comparison of LU Delay time for Norway user roams under 3G and LTE networks

34

Figure 4-23, Comparison of LU Delay time for Local user roams under 3G and LTE networks

In all the above cases it is obviously shown that the attaching latency in 3G network is more that the LTE networks and the average LU delay is almost double in 3G compare LTE network, however the difference between the delay’s upper level and downer level in LTE is more than 3G network. Generally less fluctuation has been observed while testing LU latency on 3G network in compare to testing under LTE network which means that users has more stable behavior while attaching to 3G network, however in all cases it is much faster to get attach to the LTE network in compare with respecting test under 3G network.

4.3.2 Total comparison of attach latency in 3G and 4G networks

The minimum, Maximum, average delay and standard deviation for collected data in 4G networks has been shown in table 6. The same data for collected data in 3G network shows in table 6.

Table 6, Min, Average, Standard Deviation and Max delay in 4G network UAE 3G Austria Slovenia 3G Norway 3G Sweden (Local) 3G Delay 3G Delay Delay Delay Delay

Minimum 1968 1599 1920 1627 1490

Mean 2102 1864 2118 1951 1799

Standard 112 111 114 101 86 Deviation

Maximum 2700 2120 2400 2401 1998

A trace for attaching to 4G and 3G network has been shown in Figure (4.1) and (4.7), in LTE network MME node will act as the main node and send and receive the necessary messages that need in order for UAE user to get attached to LTE network in Sweden, while this responsibility is divided between MSC and SGSN in 3G network that cause LTE network to acts faster and skip some of the procedure that will happen between the MSC and SGSN.

35 Also with regards to Figure (4.1) and Figure (4.7), the authentication time on LTE network is less than the authentication time on 3G network, the reason is that 3G network is based on SS7 protocol and use SCCP protocol for signaling purpose, while LTE network is based on diameter protocol and use S1 application protocol for the signaling purpose.

In LTE networks depending the configuration and where the operators’ nodes located, it might be possible to reduce the attach latency, while the result for LU delay in 3G network is a bit different, in 4G the message will routed towards IPX provider and from there routed towards destination while in 3G the message should reach the SCCP gateway and routed towards destination. Comparison of location updates latency for UAE, Austria, Slovenia and Norway operators shown in Figure (4.24).

Figure 4-24, Comparison of attaching latency for sample operators roam under 3G and LTE network

For have a better vision on this comparison, the attach latency has been done on specific time for the mentioned operators that has been shown in Figure (4.25).

36 Figure 4-25, Comparison of LU latency for sample operators roams on 3G and LTE network on sample times

The difference of attach latency in 3G Network is not as wide as LTE network, which means that LTE network provides the opportunity to minimize the latency as much as possible. Also the delay time difference to attached to Sweden 3G and LTE networks for these operators is the result of different nodes and interfaces in both 3G and 4G networks and different protocols that is being used by these networks.

To study more about the reason of difference in LU latency, it would be interesting to check the routing in both 3G and LTE cases. I.e. from the SGSN of the visited network (Sweden) to GGSN of the home network (UAE operator) and from the MME of the visited network to PGW of the home network, and check the routing availabilities. The result of routing availabilities towards GGSN in 3G network and PGW in LTE network is shown for UAE operator separately in Table 7, but since the operators in Austria, Slovenia and Norway have the same physical node for PGW and GGSN, the IP address would be the same in both 3G and 4G networks. The result of routing availabilities on 3G and 4G networks is shown bellow on table 7. By referring to Table 7 and Appendix 2, it can be concluded that the links are stable and there is no packet loss in case of routing under both 3G and 4G network. More details regarding the routing delay has been provided in Appendix 2.

Table 7, Routing availabilities on 3G & 4G networks UAE LTE UAE 3G Austria Slovenia Norway Delay Delay Delay Delay Delay Minimum 159.243 157.947 49.796 62.738 71.120 Mean 159.570 158.271 49.983 63.127 71.543 Maximum 160.535 158.634 50.226 63.689 71.854 Number of 1 2 2 2 4 GGSSN/PGW

By comparing the results for UAE Austria, Slovenia and Norway operators, it is obvious that the average delay time for routing towards PGW of UAE operator (159.570 ms in 4G case) is much more than the average delay time for routing towards PGW of the Austria operator (49.983), Slovenia operator (63.127) and Norway operator (71.543). This can be expected since the UAE operator GGSN node is much far compare to the other operators and the least delay is when routing towards Austria operator. This caused UAE user to have more delay in attaching to attach to the network and Austria user the less delay compare to the others since there are less hops for Austria. Also there are less hope from Sweden towards Slovenia comparing Norway as well (less firewall or routers, etc). Also operators of Austria, Slovenia and Norway use the same physical node for MME and SGSN so there will be same IP address in both cases, this conclude that there will be no difference in delay time for routing towards both GGSN and PGW of these operators.

Since there is difference in 3G and LTE networks architecture and different nodes and interfaces are used in LTE and 3G networks which may cause different LU latency in LTE network compare to 3G network.

In conclusion the attaching time is faster in 4G compare to 3G network while the LU delay deviation is less in 3G network compare to 4G and with regards to all mentioned traces and comparisons, location update latency is much less in LTE network due to its simpler nature and since there is only one main node that can handle the processes as the center of LTE

37 network and also due to the diameter protocols and interfaces that are faster in processing time such as S1, S8 and S11, etc.

38 5 CONCLUSION AND FUTURE WORK

5.1 Conclusion

This thesis discussed the quality of experience for international users roam on Sweden 3G and LTE networks. In section 4.1, four operators have been selected from UAE, Austria, Slovenia and Norway along with the local SIM card. The LU attempts have been done for sample users of these operators in different days and times and the results have been captured by the tracing tool. Using the results that has been achieved by tracing tools the attaching time latency has been estimated.

In section 4.2, the same LU attempts have been done with the local Sweden SIM card under Sweden LTE network and the results have been captured by tracing tools and LU delay time has been calculated. The achieved results has been plotted and compared with the achieved results for the sample international roamers. It concluded that there was no significant LU delay time for the Local use in compare with the Austria user which had the least routing delay, however the local user shows more stable behavior with regards to attaching time in compare with Austrian user and other international roamers.

In section 4.3, several graphs has been plotted to show the location update latency for each of these operator’s user on both 3G and LTE networks and the minimum, maximum, average delay and standard deviation has been calculated for each scenario. Then the achieved results has been discussed for 4G and 3G network and the difference on delay times for 3G and 4G networks has been explained, different comparison graphs has been plotted based on the number of trials and based on different time stamps to show the LU latency time in 3G and LTE networks. It concluded that there is a significant LU delay time for a user who is trying to attach the 4G network and 3G network and it is less LU delay for attaching to LTE network compare to 3G network, while 3G network shows more stable with regards to attaching time and the fluctuation of time delay is significantly less, this has been elaborated in the analysis part.

The LU delay has been compared for four sample operators based on the number of trials and based on different sample times and the results has been plotted on the graphs and discussed. It concluded that attaching time latency can vary based on how much the HPLMN node is far away from the VPLMN and based on different configuration. Also the operators act more stable in 3G network compare to 4G network to get attach to the network, however it is much faster to get connected to LTE network.

Answering to the Research Questions

1. How can the location update latency be evaluated for international roamer in LTE networks?

Section 4.1.1, answers the RQ1, and shows how to evaluate the LU latency for International roamers by using a tracing tools and finding the time of attachment and time of attach completing. Table 2 shows the sample LU tests and figure 4.1 shows how these delay times has been collected using the tracing tool. The delay time is the time when UE started sending the attach request until the time that attach has been completed.

2. To which extent the delay differs for an international roamer from the delay for a Local user to get connected to network in LTE Networks?

39

Section 4.2 answers RQ2, and conclude that there might not be so much difference between LU latency for local users and some of the international users that their operator’s gateway node is near to local user operator’s gateway, this can be due to configuration difference, however the attachment time is much stable for local user, i.e. the maximum delay and minimum delay does not vary for local user as much it varies for international users.

3. How the latency in LTE networks is different from 3G networks with respect to international roaming Location Update?

Section 4.3 answers the RQ3 and concludes that the LU latency in 3G networks is much more than LTE networks, in some cases the 3G networks delay time might even be double of the delay time in LTE networks, however the fluctuation for attaching to 3G network is much less than LTE network which means that the 3G networks acts more stable and the difference between minimum and maximum delays in 4G networks is more than the 3G networks, this might cause a bad customers experience and needs to be improved in the 4G networks.

5.2 Future work

In this thesis the LU delay latency for international and local users has been measured and discussed on LTE network in compare with the 3G network, also the comparison has been done between the selected international roams and between the local user and international users, but this is only the beginning, it would be necessary to find a solution on how to reduce the location update latency, since the LTE networks is all IP networks, can this delay reduce by configuring IMS system. Also how to make attaching time more stable on the LTE networks to avoid so much fluctuating.

Also it would be interesting to experience how the handover latency is different for international users roaming on 4G networks compare to 3G networks and how does the handover latency different for international users in compare with the local users.

40 BIBLIOGRAPHY

[1] "3GPP LTE". [Online]. http://www.3gpp.org/LTE. [Accessed: 5-Sep-2015] [2] M.Long, "Roaming authentication and end-to-end authentication security," 2005. [3] H. K. C. J. W. z. ,. H. W. L. C.K.Han, "Evaluation of authentication signaling loads in 3GPP LTE/SAE networks," October 2009. [4] A. S. M. Purkhiabani, "Enhanced Authentication and Key Agreement Procedure of next Generation 3GPP Mobile Networks," January 2012. [5] B. R. L. B. A.Dey, "Realization of Interworking in LTE Roaming Using a Diameter- based Interworking Function," January 2013. [6] Efort. (March 2014) "DIAMETER Signaling Network in EPS: Principles and Architecture”. [Online]. http://www.efort.com. [Accessed: 5-Sep-2015] [7] GSMA. Infocentre. [Online]. https://infocentre.gsm.org. [Accessed: 5-Sep-2015] [8] K. B. D.Gunawan, "Comparative Analysis on some possible partnership schemes of global IP exchange providers," March 2014. [Online]. http://infocentre.gsm.org. [Accessed: 5-Sep-2015] [9] S. S. R. Ahamed, "Performance analysis of Signaling System 7 (SS7) network and protocols to provide call control, remote network management and maintenance capabilities," Journal of Theoretical and Applied Information Technology, Feb. 2009. [10] “Signaling System 7 (SS7)”, Web Proforum Tutorials. [Online]. http://www.iec.org/. [Accessed: 5-Sep-2015] [11] M. N. H. V.Kumar.S.B, "Diameter-based Protocol in the IP Multimedia Subsystem," Journal of Soft Computing and Engineering (IJSCE), Jan. 2012. [12] S.Tarkoma. (2008, Nov.) T-110.5110 Computer Networks II. Tutorial. [13] “DIAMETER Architecture and Base Protocol”. [Online]. http://www.efort.com. [Accessed: 5-Sep-2015] [14] X. L. Y.Chen, "Architecture and Protocols of EPC-LTE with relay," Telecom Bretagne, Feb. February 2013. [15] A.-. . "The LTE Network Architecture, A comprehensive tutorial". Alcatel- Lucent, White Paper. [16] T.C.Balan. (2012, May) "Introducere in LTE". Tutorial. [17] S. K. P.Uppu, "QoE of Video Streaming over LTE Network," Master's thesis, Blekinge Institute of Technology, October 2013. [18] “Introduction to Evolved Packet Core”. Alcatel- Lucent, White Paper. [19] Oracle. (2013, Dec.) The Role of Diameter in All-IP, Service-Oriented Networks. Oracle, White Paper. [20] Y. O. V.Fajardo. IETF. [Online]. www.ietf.org. [Accessed: 5-Sep-2015] [21] N.Kottapalli. “Diameter and LTE Evolved Packet System”. Radisys, White Paper. [Online]. go.radisys.com. [Accessed: 5-Sep-2015] [22] E.Sutherland. (2012, Mar.) "International mobile roaming: competition, economics and regulation". [23] K.Mitchell, "LTE roaming," in 4GWE, Miami, March 2011. [24] Comfone. [Online]. www.comfone.com. [Accessed: 5-Sep-2015] [25] GSMA. IR.38, LTE and EPC Roaming Testing. [26] Osix. Polystar. [Online]. www.polystar.com. [Accessed: 5-Sep-2015]

41 [27] "Calculating the Mean and Standard Deviation". [Online]. http://www.gastro.org/. [Accessed: 5-Sep-2015]

42 APPENDIX.1

Table 8, LU test results with UAE SIM Card in 4G network LU time with UAE SIM in 4G network Sample Number Attach Request Attach Completed Delay in ms 1 13:12:27.033 13:12:28.149 1116 2 13:17:15.634 13:17:16.701 1167 3 13:23:18.784 13:23:19.980 1196 4 17:26:05.595 17:26:06.950 1355 5 13:46:43.194 13:46:44.291 1097 6 13:55:48.004 13:55:49.085 1081 7 14:05:56.144 14:05:57.338 1194 8 14:17:19.564 14:17:20.704 1140 9 14:24:50.914 14:24:52.076 1162 10 14:51:55.625 14:51:56.733 1108 11 15:00:37.463 15:00:38.608 1145 12 15:06:56.463 15:06:57.555 1092 13 15:12:53.423 15:12:54.488 1165 14 15:18:44.951 15:18:46.101 1150 15 15:23:42.542 15:23:43.678 1136 16 15:29:08.643 15:29:09.800 1157 17 15:34:37.503 15:34:38.638 1135 18 15:41:01.224 15:41:02.307 1083 19 15:47:47.983 15:47:49.075 1092 20 16:08:10.952 16:08:12.266 1314 21 16:13:13.363 16:13:14.577 1214 22 13:06:11.542 13:06:13.003 1461 23 13:16:25.114 13:16:26.426 1312 24 13:22:21.463 13:22:22.875 1412 25 13:52:33.714 13:52:35.107 1393 26 13:58:43.471 13:58:45.545 2274 27 14:05:12.225 14:05:13.642 1417 28 14:14:23.742 14:14:25.202 1460 29 14:20:48.815 14:20:50:110 1295 30 14:27:25.222 14:27:26.643 1421 31 14:39:25.342 14:39:26.696 1354 32 14:48:28:792 14:48:30:101 1309 33 15:00:32.832 15:00:34.321 1489 34 15:08:02.081 15:08:03.347 1266 35 15:13:27.672 15:13:29.127 1455 36 15:18:08.353 15:18:09.473 1120 37 15:23:58.724 15:24:00.183 1459 38 15:34:25.502 15:34:26.798 1296

43 39 15:39:37.635 15:39:38.982 1347 40 15:46:08.645 15:46:10.064 1419 41 15:51:32.842 15:51:34.285 1443 42 15:56:47.055 15:56:48.653 1598 43 16:18:47.094 16:18:48.213 1119 44 16:24:03.553 16:24:04.871 1318 45 16:28:40.852 16:28:42.170 1318 46 16:35:22.602 16:35:23.992 1390 47 16:42:57.065 16:42:58.496 1431 48 16:48:33.152 16:48:34.612 1460 49 16:54:02.013 16:54:03.429 1416 50 16:59:05.275 16:59:06.551 1276 51 17:05:28.765 17:05:30.153 1388 52 17:17:10.594 17:17:12.039 1445 53 17:21:49.113 17:21:50.499 1386 54 17:27:51.995 17:27:53.440 1445 55 17:43:35.102 17:43:36.354 1252 56 17:48:22.814 17:48:24.093 1279 57 17:53:37.054 17:53:38.546 1492 58 17:58:27.375 17:58:28.750 1375 59 18:03:29.433 18:03:30.793 1360 60 18:08:34.525 18:08:35.857 1332 61 18:15:23.862 18:15:25.488 1626 62 18:20:56.234 18:20:57.483 1249 63 09:33:16.133 09:33:17.740 1607 64 09:39:03.192 09:39:04.923 1731 65 09:43:22.025 09:43:23.483 1458 66 09:50:45.968 09:50:47.421 1453 67 09:56:10.663 09:56:12.083 1420 68 10:01:42.732 10:01:44.225 1493 69 10:14:34.904 10:14:36.463 1559 70 10:21:20.533 10:21:21.960 1427 71 10:25:27.998 10:25:29.291 1293 72 10:33:45.073 10:33:46.442 1369 73 10:57:07.744 10:57:09.336 1592 74 11:02:30.183 11:02:31.673 1490 75 11:07:47.523 11:07:49.101 1578 76 11:13:06.793 11:13:08.322 1529 77 11:19:01.782 11:19:03.106 1324 78 11:24:02.764 11:24:04.220 1456 79 12:50:47.856 12:50:49.021 1165 80 13:00:36.463 13:00:37.754 1291 81 13:05:28.324 13:05:29.687 1363 82 13:11:40.172 13:11:41.409 1237 83 13:17:19.754 13:17:21.181 1427

44 84 1538:16.954 15:38:18.441 1487 85 15:45:59.266 15:46:00.715 1449 86 15:52:40.484 15:52:41.868 1384 87 16:17:28.748 16:17:29.999 1251 88 16:21:23.432 16:21:24.681 1249 89 16:25:33.763 16:25:35.179 1416 90 10:31:19.196 10:31:20.348 1152 91 10:35:48.821 10:35:50.040 1219 92 10:39:54.563 10:39:55.870 1307 93 10:45:13.174 10:45:14.344 1170 94 13:07:05.953 13:07:07.276 1323 95 13:17:25.329 13:17:26.668 1339 96 13:23:21.272 13:23:22.608 1336 97 13:29:18.412 13:29:19.681 1269 98 13:34:45.562 13:53:46.993 1431 99 13:55:37.279 13:55:38.595 1316 100 14:51:09.744 14:51:10.899 1155 101 14:59:06.607 14:59:07.952 1345 102 18:40:19.583 18:40:20.917 1334

Table 9, LU test results with UAE SIM Card in 3G network LU time with UAE SIM in 3G network Delay in Sample Number Attach Request Attach Completed ms 1 15:41:36.213 15:41:38.381 2168 2 16:00:26.468 16:00:28.508 2040 3 16:13:47.753 16:13:49.894 2141 4 16:30:52.709 14:30:54.760 2051 5 16:36:43.747 16:36:45.787 2040 6 16:42:25.057 16:42:27.157 2100 7 16:46:37.684 16:46:39.796 2112 8 16:52:43.735 16:52:45.794 2059 9 17:03:16.079 17:03:18.251 2172 10 17:09:14.470 17:09:16.487 2017 11 17:13:53.259 17:13:55.669 2410 12 17:19:32.708 17:19:34.797 2089 13 17:37:27.583 17:37:29.843 2260 14 09:32:28.404 09:32:30.564 2160 15 09:38:02.454 09:38:04.514 2060 16 09:47:11.600 09:47:14.300 2700 17 09:55:36.730 09:55:38.789 2059 18 10:01:41.857 10:01:43.915 2058 19 10:06:35.115 10:06:37.176 2061 20 10:13:28.545 10:13:30.674 2129

45 21 10:18:17.812 10:18:19.911 2099 22 10:23:18.623 10:23:20.683 2060 23 10:27:13.663 10:27:15.741 2078 24 10:32:25.209 10:32:27.188 1979 25 10:36:48.880 10:36:50.866 1986 26 10:42:02.466 10:42:04.537 2071 27 10:47:21.197 10:47:23.165 1968 28 10:55:58.342 10:56:00.354 2012 29 11:06:01.171 11:06:03.291 2120 30 11:13:24.070 11:13:26.109 2039 31 13:05:13.868 13:05:15.999 2131 32 13:20:37.524 13:20:39.675 2151 33 13:29:40.713 13:29:42.733 2020 34 13:34:51.761 13:34:53.872 2111 35 13:39:04.871 13:39:06.931 2060 36 13:43:27.270 13:43:29.429 2159 37 13:49:41.308 13:49:43.356 2048 38 13:54:11.427 13:54:13.446 2019 39 14:01:40.405 14:01:42.586 2181 40 14:07:03.291 14:07:05.371 2080 41 15:14:17.926 15:14:20.087 2161 42 15:31:35.941 15:31:38.061 2120 43 15:39:07.619 15:39:09.667 2048 44 15:47:32.077 15:47:34.196 2119 45 16:12:59.118 16:13:01.210 2092 46 16:17:50.977 16:17:53.056 2079 47 16:23:12.247 16:23:14.395 2148 48 16:41:41.510 16:41:43.511 2001 49 16:46:33.841 16:46:35.901 2060 50 16:50:33.220 16:50:35.228 2008 51 16:54:23.579 16:54:25.599 2020 52 16:58:06.298 16:58:08.459 2161 53 17:02:23.117 17:02:25.237 2120 54 17:06:53.364 17:06:55.476 2112 55 17:12:09.834 17:12:11.842 2008 56 17:15:52.573 17:15:54.893 2320 57 17:20:19.592 17:20:21.633 2041 58 16:49:25.365 16:49:27.533 2168 59 18:14:53.823 18:14:55.803 1980 60 18:21:28.089 18:21:30.201 2112

Table 10, LU test results with Austria SIM Card in 4G network LU time with Austria SIM in 4G network

46 Sample Number Attach Request Attach Complete Delay in ms 1 13:12:33.463 13:12:34.258 795 2 13:17:21.882 13:17:22.621 739 3 13:23:25.614 13:23:26.352 738 4 13:29:00.586 13:29:01.551 965 5 13:38:05.883 13:38:06.629 746 6 13:46:48.082 13:46:48.901 819 7 13:55:53.433 13:55:54.146 713 8 14:06:02.524 16:06:03.462 938 9 14:17:26.344 14:17:27.093 749 10 14:24:59.473 14:25:00.262 789 11 14:38:16.282 14:38:17.068 786 12 14:44:58.303 14:44:59.291 988 13 14:52:05.201 14:52:05.965 764 14 15:00:29.815 15:00:30.577 762 15 15:06:57.501 15:06:58.294 793 16 15:12:59.283 15:13:00.052 769 17 15:18:53.163 15:18:54.034 871 18 15:23:48.442 15:23:49.219 777 19 15:29:14:143 15:29:14.920 777 20 15:34:42.802 15:34:43.536 734 21 15:41:03.481 15:41:04.212 731 22 15:47:45.053 15:47:45.851 798 23 15:57:43.682 15:57:44.440 758 24 16:08:17.681 16:08:18.583 902 25 16:13:21.733 16:13:22.565 832 26 13:06:17.194 13:06:18.340 1146 27 13:16:31.394 13:16:32.362 968 28 13:22:29.892 13:22:30.539 647 29 13:52:31.322 13:52:32.251 929 30 13:58:55:851 13:58:56.634 783 31 14:05:15.035 14:04:15.990 955 32 14:14:24.163 14:14:25.032 869 33 14:20:56.372 14:20:57.090 718 34 14:27:37.352 14:27:38.364 1012 35 14:39:25.213 14:39:26.045 832 36 14:48:25.862 14:48:26.987 1125 37 15:00:35.492 15:00:36.217 725 38 15:08:06.345 15:08:07.225 880 39 15:13:28.164 15:13:29.092 928 40 15:18:12.285 15:18:12.942 657 41 15:24:03.382 15:24:04.304 922 42 15:34:30.203 15:34:31.121 918

47 43 15:39:50.964 15:39:51.992 1028 44 15:46:11.992 15:46:12.916 924 45 15:51:38.015 15:51:38.959 944 46 15:56:52.342 15:56:53.030 688 47 16:18:52.123 16:18:52.863 740 48 16:24:28.114 16:24:28.798 684 49 16:28:30.292 16:28:31.122 830 50 16:35:36.231 16:35:37.241 1010 51 16:43:06.921 16:43:07.845 924 52 16:48:41.793 16:48:42.525 732 53 16:54:06.770 16:54:07.639 869 54 16:59:28.683 16:59:29.428 745 55 17:05:46.943 17:05:47.791 848 56 17:17:21.877 17:17:22.679 802 57 17:21:47.460 17:21:48.559 1099 58 17:27:46.395 17:27:47.221 826 59 17:43:47.243 17:43:47.919 676 60 17:48:49.155 17:48:49.910 755 61 17:53:29.994 17:53:30.939 945 62 17:59:02.816 17:59:03.515 699 63 18:03:21.005 18:03:21.859 854 64 18:08:46.862 18:08:47.894 1032 65 18:15:49.460 18:15:50.226 766 66 18:20:47.443 18:20:48.335 892 67 09:33:16.374 09:33:17.234 860 68 09:39:09.222 09:39:10.277 1055 69 09:43:33.984 09:43:34.983 999 70 09:50:55.363 09:50:56.181 818 71 09:56:32.414 09:56:33.299 885 72 10:01:47:073 10:01:47.927 854 73 10:14:41.514 10:14:42.214 700 74 10:21:29.127 10:21:29.837 710 75 10:25:12.563 10:25:13.600 1037 76 10:36:07.654 10:36:09.372 1718 77 10:57:04.484 10:57:05.235 751 78 11:02:58.045 11:02:58.897 852 79 11:08:05.147 11:08:06.016 869 80 11:13:47.936 11:13:49.100 1164 81 11:19:02.342 11:19:03.431 1089 82 11:24:19.223 11:24:20.118 895 83 12:50:57.297 12:50:58.183 886 84 12:58:07.024 12:58:07.886 862 85 13:05:48.245 13:05:49.172 927

48 86 13:12:07.645 13:12:08.478 833 87 13:17:44.491 13:17:45.416 925 88 15:38:14.035 15:38:15.348 1313 89 15:45:53.343 15:45:54.185 842 90 15:52:42.984 15:52:43.993 1009 91 16:17:28.664 16:17:29.525 861 92 16:21:25.185 16:21:25.928 743 93 16:25:38.124 16:25:38.848 724 94 10:31:26.155 10:31:26.878 723 95 10:35:47.739 10:35:48.549 810 96 10:40:00.655 10:40:01.484 829 97 10:45:11.971 10:45:13.155 1184 98 13:07:11.225 13:07:12.193 968 99 13:17:24.042 13:17:24.993 951 100 13:23:21.371 13:23:22.501 1130 101 13:29:18.703 13:29:19.636 933 102 13:34:54.643 13:34:55.495 852 103 13:55:49.892 13:55:50.795 903 104 14:51:16.844 14:51:17.710 866 105 14:59:11.304 14:59:12.044 740 106 18:40:18.227 18:40:18.970 743

Table 11, LU test result with Austria SIM Card in 3G network LU time with Austria SIM in 3G network Delay in Sample Number Attach Request Attach Complete ms 1 15:41:46.044 15:41:47.812 1768 2 16:00:31.608 16:00:33.277 1669 3 16:13:49.937 16:13:51.805 1868 4 16:30:41.528 14:30:43.382 1854 5 16:36:37.418 16:36:39.419 2001 6 16:42:35.778 16:42:37.737 1959 7 16:46:45.224 16:46:47.016 1792 8 16:52:48.575 16:52:50.582 2007 9 17:03:19.931 17:03:21.780 1849 10 17:09:16.650 17:09:18.550 1900 11 17:14:17.557 17:14:19.429 1872 12 17:19:36.567 17:19:38.368 1801 13 17:37:49.203 17:37:51.083 1880 14 09:32:38.616 09:32:40.483 1867 15 09:38:06.363 09:38:08.254 1891 16 09:47:18.052 09:47:19.880 1828 17 09:55:42.138 09:55:44.258 2120

49 18 10:01:27.596 10:01:29.456 1860 19 10:06:31.487 10:06:33.086 1599 20 10:06:31.287 10:06:33.086 1799 21 10:18:13.502 10:18:15.403 1901 22 10:23:13.550 10:23:15.435 1885 23 10:27:07.582 10:27:09.461 1879 24 10:32:31.260 10:32:33.140 1880 25 10:36:51.159 10:36:52.959 1800 26 10:42:06.018 10:42:08.057 2039 27 10:47:17.337 10:47:19.256 1919 28 10:44:54.194 10:55:55.893 1699 29 11:05:56.073 11:05:57.879 1806 30 11:13:26.670 11:13:28.789 2119 31 13:05:16.088 13:05:17.960 1872 32 13:20:40.556 13:20:42.496 1940 33 13:29:37.842 13:29:39.733 1891 34 13:34:53.052 13:34:54.840 1788 35 13:39:07.990 13:39:09.811 1821 36 13:43:28.890 13:43:30.689 1799 37 13:49:42.669 13:49:44.616 1947 38 13:54:07.615 13:54:09.527 1912 39 14:01:43.585 14:01:45.392 1807 40 14:07:08.404 14:07:10.172 1768 41 15:14:23.906 15:14:25.693 1787 42 15:31:38.462 15:31:40.181 1719 43 15:39:12.699 15:39:14.467 1768 44 15:47:34.655 15:47:36.525 1870 45 16:13:01.430 16:13:03.310 1880 46 16:18:02.460 16:18:04.448 1988 47 16:23:09.387 16:23:11.267 1880 48 16:41:41.990 16:41:43.842 1852 49 16:46:35.149 16:46:37.169 2020 50 16:50:29.340 16:50:31.108 1768 51 16:54:14.639 16:54:16.619 1980 52 16:58:07.586 16:58:09.598 2012 53 17:02:27.425 17:02:29.277 1852 54 17:06:49.825 17:06:51.516 1691 55 17:12:11.902 17:12:13.694 1792 56 17:15:51.303 17:15:52.922 1619 57 17:20:21.192 17:20:22.892 1700 58 16:49:24.305 16:49:26.325 2020

50 59 18:14:49.423 18:14:51.483 2060 60 18:21:26.242 18:21:28.141 1899

Table 12, LU test results with Slovenia SIM Card in 4G network LU time with Slovenia SIM in 4G network Delay in Sample Number Attach Request Attach Complete ms 1 13:12:28.948 13:12:30.321 1373 2 13:17:15.984 13:17:17.377 1393 3 13:23:18.879 13:23:20.263 1384 4 13:28:54.214 13:28:55.690 1476 5 13:37:59.802 13:38:01.140 1338 6 13:46:43.264 13:46:44.669 1405 7 13:55:48.593 13:55:49.975 1382 8 14:06:00.330 14:06:01.716 1386 9 14:17:23.284 14:17:24.821 1537 10 14:24:51.684 14:24:53.547 1863 11 14:38:11.003 14:38:12.536 1506 12 14:44:56.074 14:44:57.417 1343 13 14:52:00.063 14:52:01.396 1333 14 15:00:37.843 15:00:39.329 1486 15 15:06:57.164 15:06:58.558 1394 16 15:12:57.224 15:12:58.563 1339 17 15:18:47.722 15:18:49.548 1826 18 15:23:43.464 15:23:44.862 1398 19 15:29:09.323 14:29:10.744 1421 20 15:34:38.493 15:34:39.824 1331 21 15:41:05.182 15:41:06.592 1410 22 15:47:44.104 15:47:45.430 1326 23 15:57:38.482 15:57:39.597 1115 24 16:08:15.133 16:08:16.610 1477 25 16:13:14.679 16:13:15.939 1260 26 13:06:10.568 13:06:11.722 1154 27 13:16:23.639 13:16:24.919 1280 28 13:22:19.449 13:22:20.709 1260 29 13:52:22.081 13:52:23.469 1388 30 13:58:49.459 13:58:50.543 1084 31 14:05:11.760 14:05:12.888 1128 32 14:14:21.311 14:14:22.604 1293 33 14:20:46.571 14:20:47.679 1108 34 14:27:37.791 14:27:38.953 1162 35 14:39:22.569 14:39:23.722 1153

51 36 14:48:27.380 14:48:28.584 1204 37 15:00:34.573 15:00:35.828 1255 38 15:07:59.379 15:08:01.171 1792 39 15:13:16.810 15:13:18.064 1254 40 15:18:07.955 15:18:08.958 1003 41 15:23:54.829 15:23:56.224 1395 42 15:34:21.319 15:34:22.483 1164 43 15:39:34.810 15:39:35.861 1051 44 15:46:04.400 15:46:05.619 1219 45 15:51:30.730 15:51:31.885 1155 46 15:56:46.849 15:56:48.095 1246 47 16:18:43.191 16:18:44.353 1162 48 16:24:18.699 16:24:20.326 1627 49 16:28:38.188 16:28:39.565 1377 50 16:35:23.930 16:35:25.090 1160 51 16:42:56.151 16:42:57.396 1245 52 16:48:31.139 16:48:32.364 1225 53 16:53:57.299 16:53:58.525 1226 54 16:59:15.700 16:59:16.881 1181 55 17:05:27.508 17:05:28.867 1359 56 17:17:07.111 17:17:08.229 1118 57 17:21:54.216 17:21:55.267 1051 58 17:27:52.078 17:27:53.317 1239 59 17:43:34.089 17:43:35.261 1172 60 17:48:32.389 17:48:33.529 1140 61 17:53:31.659 17:53:32.853 1194 62 17:58:38.440 17:58:39.693 1253 63 18:03:26.539 18:03:27.690 1151 64 18:03:26.539 18:03:27.690 1151 65 18:15:21.869 18:15:23.339 1470 66 18:20:51.500 18:20:52.748 1248 67 09:33:25.591 09:33:27.061 1470 68 09:38:59.250 09:39:00.751 1501 69 09:43:21.061 09:43:22.239 1178 70 09:50:44.760 09:50:45.846 1086 71 09:56:32.082 09:56:33.216 1134 72 10:01:37.358 10:01:38.581 1223 73 10:14:30.920 10:14:32.106 1186 74 10:21:16.189 10:21:17.391 1202 75 10:25:16.561 10:25:18.015 1454 76 10:57:14.850 10:57:15.996 1146

52 77 11:02:39.032 11:02:40.189 1157 78 11:07:43.722 11:07:44.998 1276 79 11:13:15.942 11:13:17.126 1184 80 11:19:07.861 11:19:08.938 1077 81 11:23:59.981 11:24:01.026 1045 82 10:50:44.803 12:50:46.098 1295 83 12:57:51.034 12:57:52.240 1206 84 13:05:21.991 13:05:23.202 1211 85 13:11:39.830 13:11:41.158 1328 86 13:17:19.041 13:17:20.414 1373 87 15:38:09.830 15:38:11.051 1221 88 15:45:49.572 15:45:50.694 1122 89 15:52:39.544 15:52:40.954 1410 90 16:17:24.319 16:17:25.412 1093 91 16:21:22.169 16:21:23.342 1173 92 16:25:31.991 16:25:33.199 1208 93 10:31:26.158 10:31:27.470 1312 94 10:35:45.167 10:35:46.250 1083 95 10:40:02.400 10:40:03.515 1115 96 10:45:09.710 10:45:11.006 1296 97 13:06:59.239 13:07:00.420 1181 98 13:17:20.240 13:17:21.320 1080 99 13:23:31.210 13:23:32.452 1242 100 13:29:28.378 13:29:29.585 1207 101 13:34:53.699 13:34:54.813 1114 102 13:55:44.001 13:55:45.168 1167 103 14:51:08.231 14:51:09.305 1074 104 14:59:01.851 14:59:03.030 1179 105 18:40:20.886 18:40:21.985 1099

Table 13, LU test results with Slovenia SIM Card in 3G network LU time with Slovenia SIM in 3G network Delay in Sample Number Attach Request Attach Complete ms 1 15:41:46.473 15:41:48.493 2020 2 16:00:35.429 16:00:37.628 2199 3 16:13:46.345 16:13:48.404 2059 4 16:30:36.120 16:30:38.488 2368 5 16:36:32.259 16:36:34.519 2260 6 16:42:35.725 16:42:37.777 2052 7 16:46:46.636 16:46:48.596 1960 8 16:52:48.914 16:52:51.062 2148

53 9 17:03:21.039 17:03:23.092 2053 10 17:09:18.290 17:09:20.350 2060 11 17:14:18.809 17:14:20.889 2080 12 17:19:36.387 17:19:38.488 2101 13 17:37:49.243 17:37:51.262 2019 14 09:32:37.356 09:32:39.456 2100 15 09:38:07.235 09:38:09.334 2099 16 09:47:20.560 09:47:22.493 1933 17 09:55:48.532 09:55:50.611 2079 18 10:01:27.588 10:01:29.648 2060 19 10:06:30.936 10:06:33.107 2171 20 10:13:32.285 10:13:34.534 2249 21 10:18:12.684 10:18:14.824 2140 22 10:23:14.623 10:23:16.702 2079 23 10:27:07.622 10:27:09.702 2080 24 10:32:31.420 10:32:33.448 2028 25 10:36:51.300 10:36:53.439 2139 26 10:42:06.004 10:42:08.198 2194 27 10:47:18.177 10:47:20.198 2021 28 10:55:54.322 10:55:56.374 2052 29 11:05:56.092 11:05:58.471 2379 30 11:13:27.429 11:13:29.829 2400 31 13:05:16.248 13:05:18.500 2252 32 13:20:40.536 13:20:42.576 2040 33 13:29:37.814 13:29:39.873 2059 34 13:34:54.320 13:34:56.581 2261 35 13:39:07.759 13:39:09.971 2212 36 13:43:29.978 13:43:32.170 2192 37 13:49:42.688 13:49:44.748 2060 38 13:54:07.415 13:54:09.447 2032 39 14:01:44.605 14:01:46.813 2208 40 14:07:05.884 14:07:08.032 2148 41 15:14:24.074 15:14:26.133 2059 42 15:31:38.289 15:31:40.629 2340 43 15:39:12.859 15:39:14.947 2088 44 15:47:35.737 15:47:37.857 2120 45 16:13:01.498 16:13:03.539 2041 46 16:18:02.298 16:18:04.276 1978 47 16:23:09.347 16:23:11.615 2268 48 16:41:42.011 16:41:43.991 1980 49 16:46:36.061 16:46:38.112 2051

54 50 16:50:30.320 16:50:32.360 2040 51 16:54:14.659 16:54:16.707 2048 52 16:58:08.686 16:58:10.606 1920 53 17:02:27.232 17:02:29.525 2293 54 17:06:49.657 17:06:51.744 2087 55 17:12:12.204 17:12:14.302 2098 56 17:15:52.541 17:15:54.883 2342 57 17:20:21.160 17:20:23.172 2012 58 16:49:33.085 16:49:35.244 2159 59 18:14:42.622 18:14:44.762 2140 60 18:21:31.041 18:21:32.989 1948

Table 14, LU test results with Norway SIM Card in 4G network LU time with Norway SIM in 4G network Delay in Sample Number Attach Request Attach Complete ms 1 14:11:53.663 14:11:54.585 922 2 14:18:53.943 14:18:54.966 1023 3 14:21:09.552 14:21:10.250 698 4 14:46:44.144 16:46:45.109 965 5 14:50:38.493 14:50:39.284 791 6 14:53:09.374 14:53:10.106 732 7 14:56:32.262 14:56:33.195 933 8 14:58:45.875 14:58:46.782 907 9 15:01:13.373 15:01:14.054 681 10 15:04:15.115 15:04:16.354 1239 11 15:07:10.104 15:07:11.037 933 12 15:10:11.424 15:10:12.152 728 13 15:13:17.084 15:13:18.149 1065 14 15:15:44.855 15:15:45.595 740 15 15:18:09.855 15:18:10.806 951 16 15:32:18.962 15:32:20.182 1220 17 15:36:05.934 15:36:06.779 845 18 15:39:46.393 15:39:47.341 948 19 15:47:16.942 15:47:17.700 758 20 16:01:18.573 16:01:19.382 809 21 13:06:30.753 13:06:31.635 882 22 13:16:26.696 13:16:27.648 952 23 13:22:29.457 13:22.30.429 972 24 13:53:02.444 13:53:03.361 917 25 13:58:48.713 13:58:49.565 852 26 14:06:42.605 14:06:43.489 884

55 27 14:14:26.013 14:14:26.897 884 28 14:20:45.020 14:20:46.122 1102 29 14:27:37.811 14:27:38.811 1000 30 14:39:44.025 14:39:45.020 995 31 14:48:15.508 14:48:16.351 843 32 15:00:40.082 15:00:40.824 742 33 15:07:58.095 15:07:58.868 773 34 15:13:11.165 15:13:12.419 1254 35 15:18:04.632 15:18:05.438 806 36 15:23:54.513 15:23:55.310 797 37 15:34:21.242 15:34:22.566 1324 38 15:39:34.062 15:39:35.216 1154 39 15:46:03.096 15:46:04.041 945 40 15:51:30.066 15:51:31.083 1017 41 15:56:43.374 15:56:44.579 1205 42 16:18:42.135 16:18:42.998 863 43 16:24:21.432 16:24:22.507 1075 44 16:28:38.032 16:28:38.810 778 45 16:35:21.642 16:35:22.692 1050 46 16:42:54.724 16:42:55.772 1048 47 16:48:29.485 16:48:30.482 997 48 16:53:57.273 16:53:58.076 803 49 16:59:14.475 16:59:15.488 1013 50 17:05:25.368 17:05:26.908 1540 51 17:17:05.574 17:17:06.712 1138 52 17:21:45.054 17:21:45.910 856 53 17:27:47.784 17:27:48.668 884 54 17:43:30.343 17:43:31.743 1400 55 17:48:34.103 17:48:35.164 1061 56 17:53:30.565 17:53:31.507 942 57 17:58:36.955 17:58:38.138 1183 58 18:03:26.224 18:03:27.204 980 59 18:08:26.899 18:08:27.884 985 60 18:15:21.175 18:15:21.944 769 61 18:20:50.877 18:20:51.805 928 62 09:33:24.465 09:33:25.384 919 63 09:39:01.443 09:39:02.573 1130 64 09:43:23.565 09:43:24.276 711 65 09:50:46.525 09:50:47.964 1439 66 09:56:27.064 09:56:28.047 983 67 10:01:39.943 10:01:40.901 958

56 68 10:14:29.947 10:14:30.945 998 69 10:21:14.958 10:21:15.796 838 70 10:25:11.003 10:25:11.943 940 71 10:33:41.759 10:33:42.494 735 72 10:57:10.874 10:57:11.775 901 73 11:02:45.714 11:02:46.616 902 74 11:07:42.820 11:07:43.710 890 75 11:13:17.543 11:13:18.526 983 76 11:19:06.323 11:19:07.241 918 77 11:23:58.814 11:23:59.687 873 78 12:50:43.539 12:50:44.375 836 79 12:57:52.886 12:57:53.663 777 80 13:05:21.994 13:05:23.363 1369 81 13:11:35.604 13:11:36.355 751 82 13:17:17.243 13:17:18.182 939 83 15:38:12.605 15:38:13.585 980 84 15:45:49.003 15:45:49.809 806 85 15:52:38.674 15:52:39.864 1190 86 16:17:26.503 16:17:27.416 913 87 16:21:24.085 16:21:24.924 839 88 16:25:31.032 16:25:32.129 1097 89 10:31:24.693 10:31:25.544 851 90 10:35:44.882 10:35:45.784 902 91 10:39:58.312 10:39:59.265 953 92 10:45:09.324 10:45:10.442 1118 93 13:07:25.215 13:07:26.172 957 94 13:17:19.864 13:17:20.601 737 95 13:23:18.153 13:23:19.087 934 96 13:29:15.842 13:29:16.677 835 97 13:34:28.983 13:34:29.858 875 98 13:55:43.872 13:55:44.691 819 99 14:51:10.335 14:51:11.190 855 100 14:59:01.533 14:59:02.802 1269 101 18:40:17.530 18:40:18.434 904

Table 15, LU test results with Norway SIM Card in 3G network LU time with Norway SIM in 3G network Delay in Sample Number Attach Request Attach Complete ms 1 15:41:37.637 15:41:39.777 2140 2 16:01:02.008 16:01:03.909 1901 3 16:13:33.792 16:13:35.613 1821

57 4 16:31:15.180 16:31:17.140 1960 5 16:36:27.338 16:36:29.291 1953 6 16:42:27.057 16:42:29.025 1968 7 16:46:42.976 16:46:44.896 1920 8 16:52:45.283 16:52:47.195 1912 9 17:03:15.999 17:03:17.959 1960 10 17:09:14.730 17:09:16.650 1920 11 17:14:10.237 17:14:12.317 2080 12 17:19:32.967 17:19:34.976 2009 13 17:37:44.483 17:37:46.683 2200 14 09:32:33.696 09:32:35.655 1959 15 09:36:03.585 09:38:05.534 1949 16 09:47:16.972 09:47:18.920 1948 17 09:55:38.458 09:55:40.429 1971 18 10:01:31.949 10:01:33.949 2000 19 10:06:36.287 10:36:38.335 2048 20 10:13:28.705 10:13:30.772 2067 21 10:18:23.084 10:18:24.992 1908 22 10:23:18.883 10:23:20.810 1927 23 10:27:11.611 10:27:13.489 1878 24 10:32:26.708 10:32:28.668 1960 25 10:36:55.507 10:36:57.498 1991 26 10:42:00.038 10:42:01.997 1959 27 10:47:21.345 10:47:23.356 2011 28 10:55:57.002 10:55:58.913 1911 29 11:05:59.899 11:06:01.851 1952 30 11:13:23.909 11:13:25.830 1921 31 13:05:12.388 13:05:14.288 1900 32 13:20:36.996 13:20:38.924 1928 33 13:29:41.233 13:29:43.153 1920 34 13:34:52.193 13:34:54.092 1899 35 13:39:05.439 13:39:07.419 1980 36 13:43:26.310 13:43:28.291 1981 37 13:49:40.316 13:49:42.717 2401 38 13:54:02.415 13:54:04.427 2012 39 14:01:38.393 14:01:40.445 2052 40 14:07:03.184 14:07:05.211 2027 41 15:14:18.086 15:14:19.885 1799 42 15:31:35.901 15:31:37.791 1890 43 15:39:09.039 15:39:10.979 1940 44 15:47:32.325 15:47:34.196 1871

58 45 16:12:57.798 16:12:59.739 1941 46 16:18:04.009 16:18:05.969 1960 47 16:23:13.927 16:23:15.855 1928 48 16:41:39.522 16:41:41.402 1880 49 16:46:34.061 16:46:36.001 1940 50 16:50:26.760 16:50:28.660 1900 51 16:54:16.159 16:54:18.139 1980 52 16:58:07.527 16:58:09.458 1931 53 17:02:31.237 17:02:33.117 1880 54 17:06:55.084 17:06:56.964 1880 55 17:12:11.055 17:12:12.974 1919 56 17:15:52.694 17:15:54.622 1928 57 17:20:20.321 17:20:22.292 1971 58 16:49:34.105 16:49:35.732 1627 59 18:15:01.571 18:15:03.462 1891 60 18:21:33.081 18:21:34.861 1780

Table 16, LU test results with Local SIM Card in 4G network LU time with Local SIM in 4G network Delay in Sample Number Attach Request Attach Complete ms 1 09:39:58.948 09:39:59.605 657 2 09:47:53.319 09:47:54.170 851 3 09:49:34.103 09:49:34.771 668 4 09:53:14.270 09:53:14.968 698 5 09:55:50.447 09:55:51.636 1189 6 09:58:20.565 09:58:21.300 735 7 10:02:19.836 10:02:20.667 831 8 10:06:42.900 10:06:43.840 940 9 10:10:16.764 10:10:17.723 959 10 10:18:22.501 10:18:23.226 725 11 10:22:26.666 10:22:27.849 1183 12 10:24:32.706 10:24:33.598 892 13 10:43:48.917 10:43:49.858 941 14 10:53:39.910 10:53:40.713 803 15 10:56:37.025 10:56:37.901 876 16 11:03:46.885 11:03:47.940 1055 17 11:05:46.977 11:05:47.863 886 18 11:07:40.028 11:07:40.997 969 19 11:10:47.827 11:10:48.596 769 20 11:23:28.360 11:23:29.247 887 21 11:26:44.271 11:26:45.126 855

59 22 12:42:35.044 12:42:35.997 953 23 12:44:39.829 12:44:40.594 765 24 12:47:34.249 12:47:35.028 779 25 13:06:07.535 13:06:08.310 775 26 13:08:15.235 13:08:16.202 967 27 13:14.05.477 13:14:06.345 868 28 13:27:36.699 13:27:37.464 765 29 13:29:33.065 13:29:33.796 731 30 13:41:31.036 13:41:31.812 776 31 13:44:37.255 13:44:38.072 817 32 13:47:35.403 13:47:36.398 995 33 13:49:28.725 13:49:29.740 1015 34 13:55:53.024 13:55:53.995 971 35 13:59:45.525 13:59:46.448 923 36 14:06:56.126 14:06:57.020 894 37 14:12:42.994 14:12.44.146 1152 38 17:23:27.494 17:23:28.113 619 39 09:35:54.889 09:35:55.725 836 40 09:42:20.828 09:42:21.645 817 41 14:14:16.496 14:14:17.294 798 42 14:18:53.216 14:18:54.138 922 43 14:21:07.084 14:21:07.903 819 44 14:24:31.908 14:24:32.941 1033 45 14:29:12.123 14:29:13.077 954 46 14:30:37.388 14:30:38.238 850 47 14:32:59.154 14:32:59.923 769 48 14:34:36.098 14:34:36.920 822 49 14:36:16.025 14:36:16.811 786 50 14:39:25.775 14:39:26.559 784 51 14:41:03.735 14:41:04.634 899 52 14:44:51.235 14:44:52.034 799 53 14:48:10.319 14:48:11.020 701 54 14:50:38.774 14:50:39.603 829 55 14:53:06.170 14:53:07.014 844 56 14:56:31.779 14:56:32.726 947 57 14:58:46.182 14:58:46.924 742 58 15:01:12.138 15:01:13.029 891 59 15:04:13.585 15:04:14.434 849 60 15:05:32.846 15:05:33.782 936 61 15:07:09.458 15:07:10.523 1065 62 15:08:41.975 15:08:42.874 899

60 63 15:10:10.839 15:10:11.663 824 64 15:11:27.156 15:11:27.996 840 65 15:13:14.326 15:13:15.053 727 66 15:15:45.498 15:15:46.298 800 67 15:18:07.734 15:18:08.572 838 68 15:19:50.914 15:19:51.984 1070 69 15:32:17.975 15:32:18.895 920 70 15:36:04.040 15:36:04.838 798 71 15:39:44.464 15:39:45.481 1017 72 15:43:51.295 15:43:52.150 855 73 15:45:34.892 15:45:35.874 982 74 15:47:15.104 15:47:15.990 886 75 15:49:32.405 15:49:33.307 902 76 15:52:52.278 15:52:53.079 801 77 15:55:13.805 15:55:14.559 754 78 15:57:02.545 15:57:03.327 782 79 16:01:18.199 16:01:18.952 753 80 16:03:28.736 16:03:29.717 981 81 16:07:29.997 16:07:30.829 832 82 16:09:24.637 16:09:25.620 983 83 16:11:38.555 16:11:39.514 959 84 16:13:07.065 16:13:07.991 926 85 16:14:34.645 16:14:35.612 967 86 16:18:48.886 16:18:49.604 718 87 16:20:24.784 16:20:25.611 827 88 16:23:48.625 16:23:49.359 734 89 16:25:40.239 16:25:41.126 887 90 16:27:56.815 16:27:57.653 838 91 17:15:07.319 17:15:08.237 918 92 17:17:27.445 17:17:28.442 997 93 17:19:29.525 17:19:30.136 611 94 17:22:01.339 17:22:02.359 1020 95 17:26:33.955 17:26:34.854 899 96 17:48:37.438 17:48:38.255 817 97 17:50:51.886 17:50:52.947 1061 98 17:58:24.146 17:58:25.008 862 99 18:03:04.400 18:03:05.302 902 100 18:05:19.650 18:05:20.531 881

Table 17, LU test results with Local SIM Card in 3G network LU time with Local SIM in 3G network Sample Number Attach Request Attach Complete Delay in

61 ms 1 09:48:56.965 09:48:58.455 1490 2 09:51:41.666 09:51:43.365 1699 3 09:53:38.445 09:53:40.264 1819 4 09:56:51.604 09:56:53.363 1759 5 09:58:50.743 09:58:52.683 1940 6 10:00:36.983 10:00:38.903 1920 7 10:08:12.642 10:08:14.500 1858 8 10:11:38.340 10:11:40.229 1889 9 10:15:16.340 10:15:18.158 1818 10 10:19:28.178 10:19:30.078 1900 11 10:22:48.097 10:22:49.837 1740 12 10:24:51.897 10:24:53.636 1739 13 10:28:54.256 10:28:56.135 1879 14 10:32:08.616 10:32:10.614 1998 15 10:34:00.155 10:34:01.913 1758 16 10:36:13.294 10:36:15.073 1779 17 10:39:12.512 10:39:14.352 1840 18 10:43:34.892 10:43:36.589 1697 19 10:45:24.892 10:45:26.611 1719 20 10:47:32.951 10:47:34.770 1819 21 10:49:05.131 10:49:06.950 1819 22 10:50:54.950 10:50:56.669 1719 23 10:52:21.979 10:52:23.748 1769 24 10:54:32.530 10:54:34.328 1798 25 10:56:27.107 10:56:29.031 1924 26 10:58:53.690 10:58:55.547 1857 27 11:00:42.609 11:00:44.428 1819 28 11:02:57.126 11:02:58.866 1740 29 11:05:37.066 11:05:38.825 1759 30 11:08:06.905 11:08:08.766 1861 31 11:11:51.865 11:11:53.703 1838 32 11:13:40.705 11:13:42.463 1758 33 11:15:25.823 11:15:27.782 1959 34 11:16:43.583 11:16:45.323 1740 35 11:18:59.703 11:19:01.502 1799 36 13:46:09.983 13:46:11.764 1781 37 13:55:41.041 13:55:42.981 1940 38 13:57:40.201 13:57:41.980 1779 39 13:59:37.660 13:59:39.360 1700 40 14:02:47.539 14:02:49.399 1860 41 14:09:35.778 14:09:37.597 1819 42 14:12:56.397 14:12:58.356 1959

62 43 14:15:12.316 14:15:14.056 1740 44 14:32:02.731 14:34:04.551 1820 45 14:42:30.909 14:42:32.689 1780 46 14:46:42.948 14:46:44.728 1780 47 14:49:35.867 14:49:37.647 1780 48 14:55:44.385 14:55:46.146 1761 49 14:58:44.545 14:58:46.364 1819 50 15:03:25.023 15:03:26.744 1721 51 15:16:13.160 15:16:14.881 1721 52 15:24:16.879 15:24:18.698 1819 53 15:38:03.574 15:38:05.335 1761 54 15:43:39.254 15:43:41.033 1779 55 15:46:39.772 15:46:41.492 1720 56 16:37:03.239 16:37:04.979 1740 57 16:40:48.098 16:40:49.958 1860 58 16:45:09.338 16:45:11.037 1699 59 16:46:54.136 16:46:55.818 1682 60 17:00:09.493 17:00:11.393 1900

63 APPENDIX.2

UAE 3G PING 217.164.95.82 (217.164.95.82) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 217.164.95.82: icmp_seq=1 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=2 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=3 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=4 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=5 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=6 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=7 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=8 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=9 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=10 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=11 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=12 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=13 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=14 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=15 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=16 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=17 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=18 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=19 ttl=233 time=162 ms 64 bytes from 217.164.95.82: icmp_seq=20 ttl=233 time=162 ms --- 217.164.95.82 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19989ms rtt min/avg/max/mdev = 162.499/162.734/162.912/0.550 ms

PING 217.164.94.82 (217.164.94.82) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 217.164.94.82: icmp_seq=1 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=2 ttl=236 time=157 ms 64 bytes from 217.164.94.82: icmp_seq=3 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=4 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=5 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=6 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=7 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=8 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=9 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=10 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=11 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=12 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=13 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=14 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=15 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=16 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=17 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=18 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=19 ttl=236 time=158 ms 64 bytes from 217.164.94.82: icmp_seq=20 ttl=236 time=158 ms --- 217.164.94.82 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19524ms rtt min/avg/max/mdev = 157.947/158.271/158.634/0.379 ms

64 UAE 4G PING 94.57.236.16 (94.57.236.16) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 94.57.236.16: icmp_seq=1 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=2 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=3 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=4 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=5 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=6 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=7 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=8 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=9 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=10 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=11 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=12 ttl=236 time=160 ms 64 bytes from 94.57.236.16: icmp_seq=13 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=14 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=15 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=16 ttl=236 time=160 ms 64 bytes from 94.57.236.16: icmp_seq=17 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=18 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=19 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=20 ttl=236 time=159 ms --- 94.57.236.16 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19732ms rtt min/avg/max/mdev = 159.243/159.570/160.535/0.571 ms

PING 94.57.236.16 (94.57.236.16) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 94.57.236.16: icmp_seq=1 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=2 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=3 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=4 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=5 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=6 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=7 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=8 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=9 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=10 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=11 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=12 ttl=236 time=160 ms 64 bytes from 94.57.236.16: icmp_seq=13 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=14 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=15 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=16 ttl=236 time=160 ms 64 bytes from 94.57.236.16: icmp_seq=17 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=18 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=19 ttl=236 time=159 ms 64 bytes from 94.57.236.16: icmp_seq=20 ttl=236 time=159 ms --- 94.57.236.16 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19732ms rtt min/avg/max/mdev = 159.243/159.570/160.535/0.571 ms

Austria: Same IP address for 4G & 3G IP address : 194.24.157.145 & 194.24.154.145 PING 194.24.154.145 (194.24.154.145) from 80.251.193.32 : 56(84) bytes of data.

65 64 bytes from 194.24.154.145: icmp_seq=1 ttl=237 time=62.3 ms 64 bytes from 194.24.154.145: icmp_seq=2 ttl=237 time=62.1 ms 64 bytes from 194.24.154.145: icmp_seq=3 ttl=237 time=62.1 ms 64 bytes from 194.24.154.145: icmp_seq=4 ttl=237 time=62.2 ms 64 bytes from 194.24.154.145: icmp_seq=5 ttl=237 time=62.2 ms 64 bytes from 194.24.154.145: icmp_seq=6 ttl=237 time=61.9 ms 64 bytes from 194.24.154.145: icmp_seq=7 ttl=237 time=62.1 ms 64 bytes from 194.24.154.145: icmp_seq=8 ttl=237 time=62.0 ms 64 bytes from 194.24.154.145: icmp_seq=9 ttl=237 time=61.9 ms 64 bytes from 194.24.154.145: icmp_seq=10 ttl=237 time=62.1 ms 64 bytes from 194.24.154.145: icmp_seq=11 ttl=237 time=62.1 ms 64 bytes from 194.24.154.145: icmp_seq=12 ttl=237 time=62.0 ms 64 bytes from 194.24.154.145: icmp_seq=13 ttl=237 time=62.2 ms 64 bytes from 194.24.154.145: icmp_seq=14 ttl=237 time=62.1 ms 64 bytes from 194.24.154.145: icmp_seq=15 ttl=237 time=62.0 ms 64 bytes from 194.24.154.145: icmp_seq=16 ttl=237 time=62.0 ms 64 bytes from 194.24.154.145: icmp_seq=17 ttl=237 time=61.9 ms 64 bytes from 194.24.154.145: icmp_seq=18 ttl=237 time=62.0 ms 64 bytes from 194.24.154.145: icmp_seq=19 ttl=237 time=62.2 ms 64 bytes from 194.24.154.145: icmp_seq=20 ttl=237 time=62.2 ms --- 194.24.154.145 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19638ms rtt min/avg/max/mdev = 61.960/62.135/62.351/0.110 ms

PING 194.24.157.145 (194.24.157.145) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 194.24.157.145: icmp_seq=1 ttl=238 time=50.0 ms 64 bytes from 194.24.157.145: icmp_seq=2 ttl=238 time=50.0 ms 64 bytes from 194.24.157.145: icmp_seq=3 ttl=238 time=49.8 ms 64 bytes from 194.24.157.145: icmp_seq=4 ttl=238 time=50.1 ms 64 bytes from 194.24.157.145: icmp_seq=5 ttl=238 time=50.0 ms 64 bytes from 194.24.157.145: icmp_seq=6 ttl=238 time=49.7 ms 64 bytes from 194.24.157.145: icmp_seq=7 ttl=238 time=49.8 ms 64 bytes from 194.24.157.145: icmp_seq=8 ttl=238 time=50.1 ms 64 bytes from 194.24.157.145: icmp_seq=9 ttl=238 time=50.0 ms 64 bytes from 194.24.157.145: icmp_seq=10 ttl=238 time=49.9 ms 64 bytes from 194.24.157.145: icmp_seq=11 ttl=238 time=49.8 ms 64 bytes from 194.24.157.145: icmp_seq=12 ttl=238 time=49.9 ms 64 bytes from 194.24.157.145: icmp_seq=13 ttl=238 time=50.0 ms 64 bytes from 194.24.157.145: icmp_seq=14 ttl=238 time=50.2 ms 64 bytes from 194.24.157.145: icmp_seq=15 ttl=238 time=50.0 ms 64 bytes from 194.24.157.145: icmp_seq=16 ttl=238 time=49.8 ms 64 bytes from 194.24.157.145: icmp_seq=17 ttl=238 time=49.9 ms 64 bytes from 194.24.157.145: icmp_seq=18 ttl=238 time=49.9 ms 64 bytes from 194.24.157.145: icmp_seq=19 ttl=238 time=49.9 ms 64 bytes from 194.24.157.145: icmp_seq=20 ttl=238 time=50.0 ms --- 194.24.157.145 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19611ms rtt min/avg/max/mdev = 49.796/49.983/50.226/0.106 ms

Slovenia 3G & 4G IP addresses : 213.229.194.113 & 213.229.194.97 PING 213.229.194.97 (213.229.194.97) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 213.229.194.97: icmp_seq=1 ttl=48 time=63.3 ms 64 bytes from 213.229.194.97: icmp_seq=2 ttl=48 time=63.0 ms

66 64 bytes from 213.229.194.97: icmp_seq=3 ttl=48 time=62.7 ms 64 bytes from 213.229.194.97: icmp_seq=4 ttl=48 time=62.8 ms 64 bytes from 213.229.194.97: icmp_seq=5 ttl=48 time=63.1 ms 64 bytes from 213.229.194.97: icmp_seq=6 ttl=48 time=62.7 ms 64 bytes from 213.229.194.97: icmp_seq=7 ttl=48 time=63.1 ms 64 bytes from 213.229.194.97: icmp_seq=8 ttl=48 time=63.6 ms 64 bytes from 213.229.194.97: icmp_seq=9 ttl=48 time=63.3 ms 64 bytes from 213.229.194.97: icmp_seq=10 ttl=48 time=62.8 ms 64 bytes from 213.229.194.97: icmp_seq=11 ttl=48 time=62.8 ms 64 bytes from 213.229.194.97: icmp_seq=12 ttl=48 time=62.9 ms 64 bytes from 213.229.194.97: icmp_seq=13 ttl=48 time=63.3 ms 64 bytes from 213.229.194.97: icmp_seq=14 ttl=48 time=63.3 ms 64 bytes from 213.229.194.97: icmp_seq=15 ttl=48 time=62.7 ms 64 bytes from 213.229.194.97: icmp_seq=16 ttl=48 time=63.3 ms 64 bytes from 213.229.194.97: icmp_seq=17 ttl=48 time=63.4 ms 64 bytes from 213.229.194.97: icmp_seq=18 ttl=48 time=63.1 ms 64 bytes from 213.229.194.97: icmp_seq=19 ttl=48 time=63.3 ms 64 bytes from 213.229.194.97: icmp_seq=20 ttl=48 time=63.0 ms --- 213.229.194.97 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19661ms rtt min/avg/max/mdev = 62.738/63.127/63.689/0.284 ms

64 bytes from 213.229.194.113: icmp_seq=1 ttl=48 time=63.5 ms 64 bytes from 213.229.194.113: icmp_seq=2 ttl=48 time=64.0 ms 64 bytes from 213.229.194.113: icmp_seq=3 ttl=48 time=62.8 ms 64 bytes from 213.229.194.113: icmp_seq=4 ttl=48 time=62.9 ms 64 bytes from 213.229.194.113: icmp_seq=5 ttl=48 time=63.3 ms 64 bytes from 213.229.194.113: icmp_seq=6 ttl=48 time=63.1 ms 64 bytes from 213.229.194.113: icmp_seq=7 ttl=48 time=63.3 ms 64 bytes from 213.229.194.113: icmp_seq=8 ttl=48 time=63.3 ms 64 bytes from 213.229.194.113: icmp_seq=9 ttl=48 time=63.2 ms 64 bytes from 213.229.194.113: icmp_seq=10 ttl=48 time=63.3 ms 64 bytes from 213.229.194.113: icmp_seq=11 ttl=48 time=63.2 ms 64 bytes from 213.229.194.113: icmp_seq=12 ttl=48 time=62.9 ms 64 bytes from 213.229.194.113: icmp_seq=13 ttl=48 time=67.0 ms 64 bytes from 213.229.194.113: icmp_seq=14 ttl=48 time=72.7 ms 64 bytes from 213.229.194.113: icmp_seq=15 ttl=48 time=63.0 ms 64 bytes from 213.229.194.113: icmp_seq=16 ttl=48 time=65.7 ms 64 bytes from 213.229.194.113: icmp_seq=17 ttl=48 time=66.3 ms 64 bytes from 213.229.194.113: icmp_seq=18 ttl=48 time=67.4 ms 64 bytes from 213.229.194.113: icmp_seq=19 ttl=48 time=62.8 ms 64 bytes from 213.229.194.113: icmp_seq=20 ttl=48 time=63.4 ms --- 213.229.194.113 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19629ms rtt min/avg/max/mdev = 62.878/64.407/72.760/2.398 ms

Norway 3G & 4G ip addresses: 217.148.144.54 & 217.148.144.60 & 217.148.144.46 & 217.148.144.53 PING 217.148.144.54 (217.148.144.54) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 217.148.144.54: icmp_seq=1 ttl=40 time=71.3 ms 64 bytes from 217.148.144.54: icmp_seq=2 ttl=40 time=71.8 ms 64 bytes from 217.148.144.54: icmp_seq=3 ttl=40 time=71.5 ms 64 bytes from 217.148.144.54: icmp_seq=4 ttl=40 time=71.3 ms 64 bytes from 217.148.144.54: icmp_seq=5 ttl=40 time=71.8 ms

67 64 bytes from 217.148.144.54: icmp_seq=6 ttl=40 time=71.6 ms 64 bytes from 217.148.144.54: icmp_seq=7 ttl=40 time=71.8 ms 64 bytes from 217.148.144.54: icmp_seq=8 ttl=40 time=71.6 ms 64 bytes from 217.148.144.54: icmp_seq=9 ttl=40 time=71.5 ms 64 bytes from 217.148.144.54: icmp_seq=10 ttl=40 time=71.6 ms 64 bytes from 217.148.144.54: icmp_seq=11 ttl=40 time=71.3 ms 64 bytes from 217.148.144.54: icmp_seq=12 ttl=40 time=71.6 ms 64 bytes from 217.148.144.54: icmp_seq=13 ttl=40 time=71.4 ms 64 bytes from 217.148.144.54: icmp_seq=14 ttl=40 time=71.5 ms 64 bytes from 217.148.144.54: icmp_seq=15 ttl=40 time=71.3 ms 64 bytes from 217.148.144.54: icmp_seq=16 ttl=40 time=71.6 ms 64 bytes from 217.148.144.54: icmp_seq=17 ttl=40 time=71.6 ms 64 bytes from 217.148.144.54: icmp_seq=18 ttl=40 time=71.6 ms 64 bytes from 217.148.144.54: icmp_seq=19 ttl=40 time=71.1 ms 64 bytes from 217.148.144.54: icmp_seq=20 ttl=40 time=71.1 ms --- 217.148.144.54 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19581ms rtt min/avg/max/mdev = 71.120/71.543/71.854/0.422 ms

PING 217.148.144.53 (217.148.144.53) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 217.148.144.53: icmp_seq=1 ttl=40 time=72.0 ms 64 bytes from 217.148.144.53: icmp_seq=2 ttl=40 time=71.9 ms 64 bytes from 217.148.144.53: icmp_seq=3 ttl=40 time=71.9 ms 64 bytes from 217.148.144.53: icmp_seq=4 ttl=40 time=72.0 ms 64 bytes from 217.148.144.53: icmp_seq=5 ttl=40 time=71.9 ms 64 bytes from 217.148.144.53: icmp_seq=6 ttl=40 time=71.8 ms 64 bytes from 217.148.144.53: icmp_seq=7 ttl=40 time=72.0 ms 64 bytes from 217.148.144.53: icmp_seq=8 ttl=40 time=71.9 ms 64 bytes from 217.148.144.53: icmp_seq=9 ttl=40 time=71.3 ms 64 bytes from 217.148.144.53: icmp_seq=10 ttl=40 time=72.0 ms 64 bytes from 217.148.144.53: icmp_seq=11 ttl=40 time=71.9 ms 64 bytes from 217.148.144.53: icmp_seq=12 ttl=40 time=71.5 ms 64 bytes from 217.148.144.53: icmp_seq=13 ttl=40 time=71.9 ms 64 bytes from 217.148.144.53: icmp_seq=14 ttl=40 time=71.5 ms 64 bytes from 217.148.144.53: icmp_seq=15 ttl=40 time=71.8 ms 64 bytes from 217.148.144.53: icmp_seq=16 ttl=40 time=71.9 ms 64 bytes from 217.148.144.53: icmp_seq=17 ttl=40 time=72.1 ms 64 bytes from 217.148.144.53: icmp_seq=18 ttl=40 time=71.8 ms 64 bytes from 217.148.144.53: icmp_seq=19 ttl=40 time=71.7 ms 64 bytes from 217.148.144.53: icmp_seq=20 ttl=40 time=71.9 ms ^C --- 217.148.144.53 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19590ms rtt min/avg/max/mdev = 71.346/71.885/72.195/0.389 ms

PING 217.148.144.46 (217.148.144.46) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 217.148.144.46: icmp_seq=1 ttl=39 time=78.3 ms 64 bytes from 217.148.144.46: icmp_seq=2 ttl=39 time=78.7 ms 64 bytes from 217.148.144.46: icmp_seq=3 ttl=39 time=78.7 ms 64 bytes from 217.148.144.46: icmp_seq=4 ttl=39 time=78.4 ms 64 bytes from 217.148.144.46: icmp_seq=5 ttl=39 time=78.6 ms 64 bytes from 217.148.144.46: icmp_seq=6 ttl=39 time=78.2 ms 64 bytes from 217.148.144.46: icmp_seq=7 ttl=39 time=78.8 ms 64 bytes from 217.148.144.46: icmp_seq=8 ttl=39 time=78.8 ms 64 bytes from 217.148.144.46: icmp_seq=9 ttl=39 time=78.8 ms

68 64 bytes from 217.148.144.46: icmp_seq=10 ttl=39 time=78.7 ms 64 bytes from 217.148.144.46: icmp_seq=11 ttl=39 time=78.8 ms 64 bytes from 217.148.144.46: icmp_seq=12 ttl=39 time=78.4 ms 64 bytes from 217.148.144.46: icmp_seq=13 ttl=39 time=78.6 ms 64 bytes from 217.148.144.46: icmp_seq=14 ttl=39 time=78.4 ms 64 bytes from 217.148.144.46: icmp_seq=15 ttl=39 time=78.7 ms 64 bytes from 217.148.144.46: icmp_seq=16 ttl=39 time=78.8 ms 64 bytes from 217.148.144.46: icmp_seq=17 ttl=39 time=78.5 ms 64 bytes from 217.148.144.46: icmp_seq=18 ttl=39 time=78.3 ms 64 bytes from 217.148.144.46: icmp_seq=19 ttl=39 time=78.3 ms 64 bytes from 217.148.144.46: icmp_seq=20 ttl=39 time=78.3 ms --- 217.148.144.46 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19948ms rtt min/avg/max/mdev = 78.250/78.605/78.867/0.360 ms

PING 217.148.144.60 (217.148.144.60) from 80.251.193.32 : 56(84) bytes of data. 64 bytes from 217.148.144.60: icmp_seq=1 ttl=39 time=75.7 ms 64 bytes from 217.148.144.60: icmp_seq=2 ttl=39 time=74.7 ms 64 bytes from 217.148.144.60: icmp_seq=3 ttl=39 time=76.1 ms 64 bytes from 217.148.144.60: icmp_seq=4 ttl=39 time=75.0 ms 64 bytes from 217.148.144.60: icmp_seq=5 ttl=39 time=74.8 ms 64 bytes from 217.148.144.60: icmp_seq=6 ttl=39 time=75.1 ms 64 bytes from 217.148.144.60: icmp_seq=7 ttl=39 time=75.4 ms 64 bytes from 217.148.144.60: icmp_seq=8 ttl=39 time=75.1 ms 64 bytes from 217.148.144.60: icmp_seq=9 ttl=39 time=74.9 ms 64 bytes from 217.148.144.60: icmp_seq=10 ttl=39 time=75.1 ms 64 bytes from 217.148.144.60: icmp_seq=11 ttl=39 time=74.7 ms 64 bytes from 217.148.144.60: icmp_seq=12 ttl=39 time=75.0 ms 64 bytes from 217.148.144.60: icmp_seq=13 ttl=39 time=74.9 ms 64 bytes from 217.148.144.60: icmp_seq=14 ttl=39 time=75.2 ms 64 bytes from 217.148.144.60: icmp_seq=15 ttl=39 time=75.0 ms 64 bytes from 217.148.144.60: icmp_seq=16 ttl=39 time=75.2 ms 64 bytes from 217.148.144.60: icmp_seq=17 ttl=39 time=74.7 ms 64 bytes from 217.148.144.60: icmp_seq=18 ttl=39 time=74.7 ms 64 bytes from 217.148.144.60: icmp_seq=19 ttl=39 time=74.9 ms 64 bytes from 217.148.144.60: icmp_seq=20 ttl=39 time=74.9 ms --- 217.148.144.60 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19635ms rtt min/avg/max/mdev = 74.719/75.104/76.127/0.433 ms

69