3205121015
* Starting to add M2AP serialization structures. * Added M2AP procedure ids. * Added some M2AP max values. * Removing m2ap.cc for now. * Adding cause IE. * Adding dummy m2ap.cc to check correct compilation of m2ap.h * Fixed compilation issues in m2ap.h * Adding Cell Information IE. * Added Criticality diagnostics IE. * Adding eNB-MBMS-ConfigurationDataItem. * Adding MBMS-Service-Area-Id-List * Added MBMS Service Area Id. * Added Global eNB Id IE. * Added Global MCE id IE. * Added MBMS-Service-associatedLogicalM2-ConnectionItem IE. * Added MBSFN_SUBFRAME_CONFIGURATION IE * Added MCCHrelatedBCCH-ConfigPerMBSFNArea IE. * Added MCH scheduling period IE. * Added PMCH-Configuration IE. * Added Time-to-Wait IE. * Added TNL-Information IE. * Starting to add M2SetupRequest msg. * Adding M2 Setup Request message. * Fixed up enums related to initiating messages, successful outcome and unscesseful outcome. * Starting to add m2ap apck/unpack PDU functions. * Started to add a test for M2 Setup Request Pack/Unpack. * Filling in M2SetupRequest structure. * Adding packing of more IEs in the M2SetupRequest. * Starting to add unpacking functions to M2SetupRequest. * Continuing to unpack M2SetupRequest. Unpacking PLMN Identity correctly now. * Fixed up enb_id unpacking. eNB Id and eNB name unpacking correctly now. * Starting to add unpacking for dataconfiguration item. * Adding support for eCGI unpacking. * Adding MBSFN Synchronization Area id Unpacking. * Adding service area unpacking. * Added unpacking functionality to the rest of the IEs in the M2 Setup Request. Unpacking the M2 Setup Request is passing unit test. * Fized mistake in packing eNB Id. Starting to add packing to eCGI. * Starting to pack value in ENB MBMS Configuration item. * Fixed packing of ENB MBMS configuration item header. * Packing of M2 Setup request is now passing the unit test. * Starting to add M2setup response. * Starting to add packing/unpacking succeful outcome. * Starting to add M2SetupResponse to test. * Continue to add testing to setup response. Choice type seems OK. * Starting to add unpacking to MCE Id. * Adding MCEname packing/unpacking. * Continue to unpack m2setupresponse. * Adding MBMS Area Id unpacking * Added pddch length unpacking. * Adding more IE unpacking. * Adding more code to unpack M2 Setup response. * Added M2 Setup response unpacking. * Added M2 response packing. Fixed mistake on eCGI packing/unpacking, which broke M2 Setup request. * M2 setup request and response pack and unpacking seems to work. * Starting to add MBMS Session Start Request. * Continue to unpack MBMS session start request. * Added TMGI unpacking. * Continue to add unpacking to MBMS session start request * Starting to add TNL Information unpacking * Added unpack for MBMS session start request. * Strating to add MBMS session start request packing. * Adding MCE MBMS M2AP Id packing. * Added MBMS Session Start Reqeust pack and unpack. * Added MBMS Session start response packing/unpacking. * Starting to add unpacking of MBMS Scheduling information. * Adding MCCH Update time Unpacking. * Adding MBSFN Area Configuration List Unpacking. * Starting to add unpack PMCH configuration Item. * Adding AllocatedSubframesEnd unpack * Fixed multiple mistakes in unpacking PMCH configuration. * Unpacking MCH Scheduling Period * Continue to unpack MBMS Session List Per PMCH Item. * Added unpacking of PMCH Configuration List. Starting to add unpacking of MBSFN Subframe Configuration List. * Adding radioframe allocation period and offset unpacking. * Added unpacking of MBMS Scheduling Information (needs testing.) * Added more testing to MBMS Scheduling Info. * Small commit. * Added more testing to the unpacking of MBMS Scheduling Information. Unpacking correctly now. * Continue to pack MBMS Scheduling information. Packing PMCH Configuration. * Fixed mistach in packing PMCH configuration list. * Adding more packing to MBMS scheduling info message. * Fixed more mistakes in MBMS Scheduling information packing. Passing tests now. * Added MBMS Scheduling Information Response. * Remove debug prints. |
6 years ago | |
---|---|---|
cmake/modules | 6 years ago | |
debian | 6 years ago | |
lib | 6 years ago | |
srsenb | 6 years ago | |
srsepc | 6 years ago | |
srsue | 6 years ago | |
.clang-format | 6 years ago | |
CHANGELOG | 6 years ago | |
CMakeLists.txt | 6 years ago | |
COPYRIGHT | 8 years ago | |
CTestConfig.cmake | 7 years ago | |
CTestCustom.cmake.in | 7 years ago | |
LICENSE | 7 years ago | |
README.md | 6 years ago | |
cmake_uninstall.cmake.in | 11 years ago |
README.md
srsLTE
srsLTE is a free and open-source LTE software suite developed by SRS (www.softwareradiosystems.com).
It includes:
- srsUE - a complete SDR LTE UE application featuring all layers from PHY to IP
- srsENB - a complete SDR LTE eNodeB application
- srsEPC - a light-weight LTE core network implementation with MME, HSS and S/P-GW
- a highly modular set of common libraries for PHY, MAC, RLC, PDCP, RRC, NAS, S1AP and GW layers.
srsLTE is released under the AGPLv3 license and uses software from the OpenLTE project (http://sourceforge.net/projects/openlte) for some security functions and for RRC/NAS message parsing.
Common Features
- LTE Release 8 compliant (with selected features of Release 9)
- FDD configuration
- Tested bandwidths: 1.4, 3, 5, 10, 15 and 20 MHz
- Transmission mode 1 (single antenna), 2 (transmit diversity), 3 (CCD) and 4 (closed-loop spatial multiplexing)
- Frequency-based ZF and MMSE equalizer
- Evolved multimedia broadcast and multicast service (eMBMS)
- Highly optimized Turbo Decoder available in Intel SSE4.1/AVX2 (+100 Mbps) and standard C (+25 Mbps)
- MAC, RLC, PDCP, RRC, NAS, S1AP and GW layers
- Detailed log system with per-layer log levels and hex dumps
- MAC layer wireshark packet capture
- Command-line trace metrics
- Detailed input configuration files
srsUE Features
- Cell search and synchronization procedure for the UE
- Soft USIM supporting Milenage and XOR authentication
- Hard USIM support using PCSC framework
- Virtual network interface tun_srsue created upon network attach
- 150 Mbps DL in 20 MHz MIMO TM3/TM4 configuration in i7 Quad-Core CPU.
- 75 Mbps DL in 20 MHz SISO configuration in i7 Quad-Core CPU.
- 36 Mbps DL in 10 MHz SISO configuration in i5 Dual-Core CPU.
srsUE has been fully tested and validated with the following network equipment:
- Amarisoft LTE100 eNodeB and EPC
- Nokia FlexiRadio family FSMF system module with 1800MHz FHED radio module and TravelHawk EPC simulator
- Huawei DBS3900
- Octasic Flexicell LTE-FDD NIB
srsENB Features
- Round Robin MAC scheduler with FAPI-like C++ API
- SR support
- Periodic and Aperiodic CQI feedback support
- Standard S1AP and GTP-U interfaces to the Core Network
- 150 Mbps DL in 20 MHz MIMO TM3/TM4 with commercial UEs
- 75 Mbps DL in SISO configuration with commercial UEs
- 50 Mbps UL in 20 MHz with commercial UEs
srsENB has been tested and validated with the following handsets:
- LG Nexus 5 and 4
- Motorola Moto G4 plus and G5
- Huawei P9/P9lite, P10/P10lite, P20/P20lite
- Huawei dongles: E3276 and E398
srsEPC Features
- Single binary, light-weight LTE EPC implementation with:
- MME (Mobility Management Entity) with standard S1AP and GTP-U interface to eNB
- S/P-GW with standard SGi exposed as virtual network interface (TUN device)
- HSS (Home Subscriber Server) with configurable user database in CSV format
Hardware
The library currently supports the Ettus Universal Hardware Driver (UHD) and the bladeRF driver. Thus, any hardware supported by UHD or bladeRF can be used. There is no sampling rate conversion, therefore the hardware should support 30.72 MHz clock in order to work correctly with LTE sampling frequencies and decode signals from live LTE base stations.
We have tested the following hardware:
- USRP B210
- USRP B205mini
- USRP X300
- limeSDR
- bladeRF
Build Instructions
- Mandatory requirements:
- Common:
- cmake https://cmake.org/
- libfftw http://www.fftw.org/
- PolarSSL/mbedTLS https://tls.mbed.org
- srsUE:
- Boost: http://www.boost.org
- srsENB:
- Boost: http://www.boost.org
- lksctp: http://lksctp.sourceforge.net/
- config: http://www.hyperrealm.com/libconfig/
- srsEPC:
- Boost: http://www.boost.org
- lksctp: http://lksctp.sourceforge.net/
- config: http://www.hyperrealm.com/libconfig/
- Common:
For example, on Ubuntu 17.04, one can install the required libraries with:
sudo apt-get install cmake libfftw3-dev libmbedtls-dev libboost-program-options-dev libconfig++-dev libsctp-dev
or on Fedora:
dnf install cmake fftw3-devel polarssl-devel lksctp-tools-devel libconfig-devel boost-devel
Note that depending on your flavor and version of Linux, the actual package names may be different.
-
Optional requirements:
- srsgui: https://github.com/srslte/srsgui - for real-time plotting.
- libpcsclite-dev: https://pcsclite.apdu.fr/ - for accessing smart card readers
-
RF front-end driver:
Download and build srsLTE:
git clone https://github.com/srsLTE/srsLTE.git
cd srsLTE
mkdir build
cd build
cmake ../
make
make test
Install srsLTE:
sudo make install
sudo srslte_install_configs.sh
This installs srsLTE and also copies the default srsLTE config files to the user's home directory (~/.srs).
Execution Instructions
The srsUE, srsENB and srsEPC applications include example configuration files that should be copied (manually or by using the convenience script) and modified, if needed, to meet the system configuration. On many systems they should work out of the box.
By default, all applications will search for config files in the user's home directory (~/.srs) upon startup.
Note that you have to execute the applications with root privileges to enable real-time thread priorities and to permit creation of virtual network interfaces.
srsENB and srsEPC can run on the same machine as a network-in-the-box configuration. srsUE needs to run on a separate machine.
If you have installed the software suite using sudo make install
and
have installed the example config files using sudo srslte_install_configs.sh
,
you may just start all applications with their default parameters.
srsEPC
On machine 1, run srsEPC as follows:
sudo srsepc
Using the default configuration, this creates a virtual network interface named "srs_spgw_sgi" on machine 1 with IP 172.16.0.1. All connected UEs will be assigned an IP in this network.
srsENB
Also on machine 1, but in another console, run srsENB as follows:
sudo srsenb
srsUE
On machine 2, run srsUE as follows:
sudo srsue
Using the default configuration, this creates a virtual network interface named "tun_srsue" on machine 2 with an IP in the network 172.16.0.x. Assuming the UE has been assigned IP 172.16.0.2, you may now exchange IP traffic with machine 1 over the LTE link. For example, run a ping to the default SGi IP address:
ping 172.16.0.1
Support
Mailing list: http://www.softwareradiosystems.com/mailman/listinfo/srslte-users