In document Terminal LTE flexível (Page 86-89)

6.2 Setup and Tools

6.2.1 Setup

In Figure 6.1 is the block diagram of the final setup, with the different UEs used for testing and their radio configurations, described in the previous chapter. The IP addresses assigned to each component are also presented in the Figure.

The LTE network is identified by, amongst others, the PLMN-ID. For testing, it is essential to create a new PLMN-ID for the network, so it is clear that the UE is being attached to the correct LTE network and also for legal issues. There are three main operational networks in Portugal, Vodafone (26801), NOS (26803) and altice MEO (26806). The first three digits represent the MCC, 268 for Portugal, and the last digits represent the MNC. As 08 is not attributed to a specific LTE network, it will be used as the setup’s MNC. The new PLMN-ID (26808) has to be configured in the OAI eNB, UE, MME and SPGW nodes (every step is described in Appendix C).

Other parameters need to be set on the EPC side, namely the integrity and ciphering algorithms to be used, the IP network settings and the MySQL server configurations. On the eNB side, parameters like the duplex mode (TDD/FDD), E-UTRA frequency band (specify- ing the downlink and uplink frequencies), number of LTE resource blocks, transmission and reception gain, reference signal power and IP network settings have to be configured. For transmission in unstandardized and unlicensed bands, or in bands not programmed in OAI, such as FDD’s Band 31, additional changes have to be made in the source code of the eNB and UE, otherwise the system will not recognize them, all described in Appendix C.

The UE emulates an USIM card, configured using a single file. This file contains infor- mation regarding the known PLMNs to the UE, as well as the typical UE and USIM card parameters, IMSI, IMEI, K and OPc. These values are represented in Table 6.1.

Table 6.1: Emulated USIM card for the UE. Configuration File USIM Card K 8baf473f2f8fd09487cccbd7097c6862 OP 11111111111111111111111111111111 OPc 8e27b6af0e692e750f32667a3b14605d

IMSI 268080000000009

IMEI 356092040793012

The UEs will vary depending on the setup (represented by (a) and (b), in Figure 6.1 ), but the eNB and EPC remain the same. They’re ran on separate computers and are both connected by an Ethernet cable. For the EPC, the following network settings are applied.

ˆ Ethernet port 0, eth0: connection to the outside world (Internet), with IPv4 address, MTU size of 1500.

ˆ Ethernet port 1, eth1: connection to the eNB’s computer, with IP and Maximum Transmission Unit (MTU) size of 1536.

Furthermore, in the SPGW node, a pool of IPv4 addresses to be assigned to the UEs is configured (, with the first address reserved for the GTP network device ( The network’s DNS servers communicated to the UEs are and

On the eNB side, only one port is required to communicate with the EPC, but the setup’s computer has two Ethernet ports, so it will be used for a different purpose.

Figure 6.1: Final implemen tation setup, including tw o differen t UEs, v arious radio configurations, the p ossibilit y to sh are mobile data through a Wi-Fi hotsp ot , and the IPs assigned to eac h comp onen t.

ˆ Ethernet port 1, eth1: connection to the EPC’s computer, with IP and MTU size of 1536.

ˆ Ethernet port 0, eth0: this port is only used for the SBC setup, to establish an SSH remote connection with the board running the OAI UE, saving computing resources by eliminating the graphical interface processing. The configured IP is and MTU size of 1536.

The UE won’t require any prior IP address configuration, unless it is running in the UP Squared SBC. If so, one of its Ethernet ports will be configured with the IPv4 address and connected to the eNB, to be remotely controlled. Commercial UEs

Aside from the UEs implemented with software radio, two commercial UEs (smartphones, in this case) are used for testing and are represented below:

ˆ Samsung Galaxy S4 (GT-i9295) [Sam17]. ˆ OnePlus 3 (A3003) [One17].

Table 6.2 depicts the frequency bands recognized by the two smartphones, in both TDD and FDD duplex modes. Some of these will be used for testing, as is later discussed in 6.2.3. In order to connect the UEs to the network, one can’t use a regular network operator’s USIM card, as some parameters (K, OP) are only known by the network operator itself and can’t be added into OAI’s subscriber database by a regular user. Therefore, a programmable USIM card has to be used, so every parameter will be programmed by the user.

Table 6.2: Frequency bands supported by the commercial UEs.

FDD TDD Frequency Bands 1 2 3 4 5 7 8 12 17 20 28 30 38 39 40 41 Samsung Galaxy S4 X X X X X X OnePlus 3 X X X X X X X X X X X X X X

USIM cards The parameters for the USIM cards used in the commercial UEs are in Table 6.3 and were also inserted in the HSS database. The programming of these is described in Appendix C. Photos

In this section, photos of the setup are shown. Figure 6.2 shows the setup for the UE running in a single-board computer. On the UE label, the USRP B200mini is also included, as it joined together with the UP Squared in a 3D printed holder (development process in Appendix D). Figure 6.3 shows the used RF components, each being labeled in the photo except for the RF attenuators.

Table 6.3: USIM cards parameters: card 1 is used on Samsung Galaxy S4 and card 2 on the OnePlus 3.

Card 1 Card 2

K 8baf473f2f8fd09487cccbd7097c6862 00112233445566778899aabbccddeeff OP 11111111111111111111111111111111 01020304050607080910111213141516 OPc 8e27b6af0e692e750f32667a3b14605d 0ed47545168eafe2c39c075829a7b61f

IMSI 268080000000002 26808000000003

SPN1 OpenAirInterface OpenAirInterface

Figure 6.2: Setup for the UE running in a single-board computer. On the UE label, the USRP B200mini is also included.

In document Terminal LTE flexível (Page 86-89)