1 Introduction
2 Background on Mobile Networks
-
The Mobility Management Entity (MME) that controls the connection and the user’s mobility between base stations, and maintains a single session for a particular UE between all the entities.
-
The Home Subscriber Server (HSS) that maintains the users’ database and the security of the connections.
-
One or more Serving and Packet Data Network Gateways (SGW and PGW) that connect the RAN with the EPC and the EPC with external networks, respectively.
3 EuWireless User Profiles and Design Principles
3.1 User Profiles
3.1.1 Researcher
3.1.2 Service Provider
3.1.3 EuWireless Subscribers
3.2 Design Principles
-
Support for isolated concurrent EuW users: slices from both researchers and service providers should be able to run in parallel, in a way that physical resources are shared among them without interfering with each other.
-
Pan-European deployment: since one of the objectives is to offer the same access opportunities to all European researchers regardless of their location, we propose a distributed infrastructure in which the coverage area is extended by deploying cross-country PoPs, and each EuW user accesses to the closest available PoP.
-
Scalable PoPs as the main core objects: the distribution of the architecture is possible thanks to the deployment of sets of resources in different locations across Europe, the so-called PoPs, increasing the infrastructure’s local performance and scalability. Hence, the project can be extended by deploying a PoP in a new location and interconnecting that PoP with the rest of the infrastructure to make its resources available for every EuW user.
-
Adaptable to integrate new mobile technologies: even though 5G technology is yet to be deployed on a large scale, the project aims at integrating novel technologies to be tested together with the current generation of mobile networks. Thus, we expect the project to allow an abstraction and extension such that new paradigms can be easily accommodated.
-
Fully automated: the process of slice provisioning should be automatic, enabling EuW users to define their slices and reserve the resources they need, whereas EuWireless applies fair user policies to prevent resource exhaustion from greedy experiments.
4 Architecture of EuWireless PoP
-
EuW Portal and API: it is the entry point for EuW users to define and manage slices for experimentation.
-
Inter PoP: this layer has a global view of the EuWireless infrastructure and performs tasks involving multiple PoPs and slices. The PoP Directory is located in this layer and stores information on the rest of the PoPs comprising the infrastructure, including their local resources (not their availability) and their authorized users.
-
Intra Slice: this layer is in charge of managing a slice previously designed and deployed, which can span across one or multiple PoPs. The Slice + NF Catalogue entity is located in this layer, and stores the mapping between the slice’s abstract description and the actual resources. Since it is likely that a EuW user will employ a slice template or reuse the same slice description several times, the mapping information will be available to speed up the slice construction phase.
-
Intra PoP: this layer interacts with a PoP’s local resources. The local resources can have different administrative domains; that is, a PoP’s local resources can be owned by the EuWireless infrastructure, by a commercial MNO that shares its resources with EuWireless, or by a researcher that wants to include his/her resources into an EuW slice. This layer includes the Infrastructure Catalogue, which keeps information on the resources locally managed by the PoP and their availability.
-
Communication: this layer provides the connectivity services to the upper layers in order to effectively communicate with other PoPs or with the local resources.
4.1 Slice Creation
4.2 Slice Release
4.3 Other Entities
5 Integration of Resources in the PoP and Proof-of-Concept
Requirements | CPU | 1 processor |
RAM | 4 GB | |
HDD | 25 GB | |
OS | Ubuntu 18.04 distribution with NextEPC software | |
Ports | S1-MME | Connects the EPC with one or multiple eNBs and transports control plane information |
S1-U | Connects the EPC with one or multiple eNBs and transports data plane information | |
SGi | Connects the EPC with external IP networks | |
Attributes | Location | PoP selected to instantiate the VM with the EPC software |
PLMN | Public Land Mobile Network, includes the Mobile Country Code (MCC) and Mobile Network Code (MNC) | |
TAC | Tracking area code | |
IP Pool | List of IP addresses available for the UEs | |
Subscribers | List of subscribers identified by their International Mobile Subscriber Identities (IMSIs) | |
APN | Access Point Name of the network providing internet access | |
Auth. | K code and OP/OPc authentication | |
param. | parameters | |
Primitives | Reservation | Locates the requirements needed to instantiate the VM in the PoP and the links available for definition of the ports |
Activate | Installs the OS, configures the attributes specified by the EuW user, and initializes the entities composing the EPC | |
Deactivate | Stops the VM and the traffic flow, but maintains the existing connections and resources | |
Reconfigure | Changes configuration parameters and attributes after the first instantiation | |
Query | Provides information about the state of the resource without triggering a transition among states | |
Release | Deletes the VM and links associated to the ports, returning the resources to the pool available in the PoP |
Ports | S1 | Connects the eNB with the EPC |
---|---|---|
Attributes | Location | PoP where the resource is placed |
IP address | If the resource has no IP address fixed, IP address of the eNB to configure the EPC accordingly | |
Primitives | Reservation | Locates the physical device in the area requested and the availability of the specific links for the connection |
Activate | Set the link to allow the traffic flow between the eNB and the EPC | |
Deactivate | Stops the traffic flow, but maintains the existing connection and the resource | |
Reconfigure | Changes the value of the IP address after the first instantiation | |
Query | Provides information about the state of the resource without triggering a transition among states | |
Release | Deletes the link associated to the port, returning the resource to the pool of resources available in the PoP |
5.1 Proof-of-Concept
6 Related Work
Project | Coverage | Mobility | Spectrum | Extensible | Orchestration |
---|---|---|---|---|---|
EuWireless | Pan-European deployments | Eduroam, V2X | Commercial (shared LSA) | Yes | Multi-domain, distributed |
FIRE | Fixed labs (Europe) | Per testbed | Per testbed | Per testbed | Per testbed |
GENI | US universities | Per project | Educational broadband | Per project | Per project |
COSMOS | US NY city sector | V2X | Commercial 5G | Yes | Centralized OMF |
Powder | US Salt Lake city sector | V2X | Commercial 5G | Yes | Centralized Emulab |
5Gtango | No | No | No | Yes | Centralized OSM |
MATILDA | No | No | No | Yes | Multi-site, centralized |
SliceNet | No | No | No | Yes | Multi-domain, cross-plane |
5GENESIS | EU city sectors | Yes | Commercial 4G and 5G | Yes | Centralized, per platform |
5G-VINNI | EU city sectors | Yes | Commercial 4G and 5G | Yes | Centralized, per platform |
5G EVE | EU city sectors | Yes | Commercial 4G and 5G | Yes | Centralized, per platform |