5G/NextG

Team: Jeff Acevedo | Stanislav Ceman | Ryan Lin | Sreeram Mandava | Aleksa Samardzija | Nikhil Sampath | Sanskar Shah | Steve Shin | Xoua Thao

Project Objectives

The ultimate goal of the project is to develop an open-source implementation of a 5G system. Specific tasks included implementing an end-to-end session of the system from user equipment to the internet, and developing network control and management applications. All work was done in the context of Open RAN (O-RAN), which seeks to create a more disaggregated and flexible architecture of the traditional radio access network (RAN). A diagram displaying the basic O-RAN architecture is shown below.

A central aspect of the project was developing applications (rApps) and framework services in the Service Management and Orchestration (SMO) framework. The three rApps developed by the team were the Security rApp, Resilience rApp, and Frequency/Spectrum management rApp. Functions of the framework services included topology maintenance, topology visualization, alarm generation, and spectrum sensing. A block diagram and sequence diagram detailing the layout and dataflow of the SMO framework are shown below.

Topology Scenario

To understand and convey the use of the applications and framework services, the group developed a realistic situation in which the work would apply. Say there is a straight-line road running east-west. An example of such a road is shown below, at latitude 38.892 (Washington D.C.). UEs(cellular devices) and RUs could be distributed along the road. There is an assumption that UEs can only connect to a particular RU when the distance is within a certain threshold. The ultimate purpose of the applications is to maintain constant connectivity for a dynamic or static UE along this road. If a UE is connected to multiple paths, connectivity can still be maintained if one of the paths is compromised. Additionally, the transmission of data can be optimized among the paths.

Weekly Slides

Week 1: ​https://docs.google.com/presentation/d/12tB8qu7PKzh8Vf91PTPGVp_zUQDTg3FHjTDCSrbz3OU/edit?usp=sharing

Week 2: ​https://docs.google.com/presentation/d/1BG-Ic3cOMBmDDZqHKv0XwhQrPxmHiZBA1T47vDEJ4ic/edit?usp=sharing

Week 3: ​https://docs.google.com/presentation/d/1ki9sL52asnUo6WTF8jv6MEudg8ONSFogNYiSJHvBZ4U/edit?usp=sharing

Week 4: ​https://docs.google.com/presentation/d/1G3B79Km7aUUF_xqcfx2OCIzeoE0pBuLZj6MlBGVAii8/edit?usp=sharing

Week 5: ​https://docs.google.com/presentation/d/1OS8VFtsQ5ILXReiLvHyejSO0vgwyX_5eUyWc2-GP_84/edit?usp=sharing

Week 6: ​https://docs.google.com/presentation/d/1rORzg2HuLZ9SxoOVcGMePYcQY3u_tkATb7bNcjwagXI/edit?usp=sharing

Week 7: ​https://docs.google.com/presentation/d/1GB9vG1cwhJmrmIPBrwt6um108A3Dv3bwhitFh3CY5f8/edit?usp=sharing

Week 8: ​https://docs.google.com/presentation/d/1edx007kB5G_o_x5JgZPQ-HRJM-ZRZyGK-N0pWfACPFA/edit?usp=sharing

Week 9: ​https://docs.google.com/presentation/d/1c6ID0c8H2XI0_f_ypQehksXWcXTJUp20SNDlI2dtnMU/edit?usp=sharing

Radio System Implementation

Amarisoft

OpenAirInterface

SMO Framework Services and Applications

Framework Services

Security rApp

The Security rApp aims to provide closed-loop control in the SMO. This means that the network would be automatically configured based on changes. The rApp reads information from a Kafkabus regarding information about threats to the system. The existing code makes a graph out of the topology information contained in a JSON file. The program then receives and parses alarms and responds accordingly. In the event of a compromised part, the rApp quarantines the node and updates the access status of the node within the graph object.

Topology/Resilience rApp

One method of increasing the resilience and efficiency of a RAN system is to have a single UE device connected to two RAN networks. The individual networks are managed by their own SMOs, which are in turn managed by a master SMO. Using the two networks, the data transfer can be optimized for speed and efficiency. Additionally, if one of the networks were to be compromised, connectivity can be maintained through the other network. A drawing of the system is shown below. The Resilience rApp in the master SMO can interact with the Resilience rApps in the two networks in order to learn about the topology and the state of the two networks. The master SMO can handle optimization and maintain constant connectivity for the UE. Topology information in the code can be tagged with attributes including cost, availability, performance, and security. This information can be used for optimization purposes.