## Definitions
The following naming conventions were used:
●	*AWS-i* - denotes a region of AWS (Amazon Web Services), as defined in *list-1*.
●	*Challenge-i* - denotes a featured challenge with index *i*.
●	*cdgeb-probe-i* - denotes the *i'th* probing server used to probe the cloud.
●	*cdgeb-server-i* - denotes the *i'th* front-end server in the cloud.
●	*cdgeb-file-i* - denotes the *i'th* file stored in the cloud storage service.


## System Model
The first mockup CDGeB service comprises S3 buckets, sample files stored on S3 buckets, and EC2 instances functioning as front-end servers of our application. It relies on a 3-tier architecture (storage-app-client) without load balancing or dynamic caching abilities of cloud-based applications. 

17 instances of AWS EC2, each in a different region, were set up. The instances are denoted using a numerical convention throughout this challenge: *cdgeb-server-01*, *cdgeb-server-02*, etc.

The same 17 regions were used to employ AWS S3 buckets. Each bucket stores a single file, named with similar convention - *cdgeb-file-01*, *cdgeb-file-02*, etc. However, THE NUMBERING OF FILES IS NOT THE SAME AS THE NUMBERING OF EC2 SERVERS! E.g., *cdgeb-file-01* does not imply that the file is located in the same region as with *cdgeb-server-01*.

    Region ID	Region Name				Server ID
    AWS-01	US East (N. Virginia)		cdgeb-server-01
    AWS-02	EU (London)					cdgeb-server-02
    AWS-03	South America (São Paulo)	cdgeb-server-03
    AWS-04	Asia Pacific (Tokyo)		cdgeb-server-04
    AWS-05	Asia Pacific (Singapore)	cdgeb-server-05
    AWS-06	Canada (Central)			cdgeb-server-06
    AWS-07	US East (Ohio)				cdgeb-server-07
    AWS-08	US West (N. California)		cdgeb-server-08
    AWS-09	US West (Oregon)			cdgeb-server-09
    AWS-10	Asia Pacific (Mumbai)		cdgeb-server-10
    AWS-11	Asia Pacific (Osaka)		cdgeb-server-11
    AWS-12	Asia Pacific (Seoul)		cdgeb-server-12
    AWS-13	Asia Pacific (Sidney)		cdgeb-server-13
    AWS-14	EU (Frankfurt)				cdgeb-server-14
    AWS-15	EU (Ireland)				cdgeb-server-15
    AWS-16	EU (Paris)					cdgeb-server-16
    AWS-17	EU (Stockholm)				cdgeb-server-17
*List 1 - AWS regions, and corresponding front-end server names.*

To probe the front-end servers, a total of 14 instances of Google Cloud Platform services were employed as Internet clients, distributed across the following locations:

    Probe ID	Region Name			Region Code
    cdgeb-probe-01	Montreal	northamerica-northeast1
    cdgeb-probe-02	Toronto		northamerica-northeast2
    cdgeb-probe-03	Sao Paulo	southamerica-east1
    cdgeb-probe-04	Oregon		us-west1
    cdgeb-probe-05	Los Angeles	us-west2
    cdgeb-probe-06	Warsaw		Europe-central2
    cdgeb-probe-07	Finland		Europe-north1
    cdgeb-probe-08	Madrid		Europe-southwest1
    cdgeb-probe-09	Doha		Me-central1
    cdgeb-probe-10	Tel Aviv	Me-central2
    cdgeb-probe-11	Taiwan		Asia-east1
    cdgeb-probe-12	Hong Kong	Asia-east2
    cdgeb-probe-13	Tokyo		Asia-northeast1
    cdgeb-probe-14	Osaka		Asia-northeast2
*List 2: Locations of probing servers used throughout the benchmark.*

![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F12498741%2Fe1bad1bdd0a14310055e8d018e063497%2Finfrastructure.jpg?generation=1694031547812556&alt=media)
                                  *Figure 1: Illustration of the probing process*

### The measurement procedure
Each one of the probes (*cdgeb-probe-i*) retrieves each one of the files (*cdgeb-file-i*) through multiple front-end servers (*cdgeb-server-i*). 

## Dataset Description
The following section describes the first CDGeB dataset. The dataset consists of multiple series of measurements, and each line in the dataset contains the following information:
●	Difficulty - *Challenge-i*, (i=1,2)
●	Probe - *cdgeb-probe-i*, (i=1..14)
●	Front Server - *cdgeb-server-i*, (i=1..17)
●	Data File - *cdgeb-file-i*, (i=1..17)
●	RTT - values of 20 sequential probings in units of seconds.

*Challenge-1* and *Challenge-2* correspond to two difficulty levels. *Challenge-1* consists of the measurement of files 1-5 (*cdgeb-file-01*, .., *cdgeb-file-05*), and *Challenge-2* consists of the measurement of files 6-17.

In both Challenge-1 and Challenge-2, a random set of 8 front-end servers is chosen for the retrieval of each individual file. However, the challenges differ in their level of difficulty. In Challenge-1, which is considered the easier challenge, 1 server out of the 8 is known to be located in the same geographical region as the file itself. In contrast, in Challenge-2, none of the front-end servers within the set reside in the same geographical region as the corresponding file.

![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F16558320%2F166358a74b028a71e45e4786cdd64ede%2FScreenshot%202023-09-18%20003017.png?generation=1694991095710504&alt=media)
*Table 1: Dataset Demonstration*


## Goal
The primary goal of the challenges is to ascertain the AWS region associated with each individual data file.