Changes between Version 21 and Version 22 of Other/Summer/2023/5G6G


Ignore:
Timestamp:
Aug 8, 2023, 3:08:02 PM (16 months ago)
Author:
NikhilSampath
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Other/Summer/2023/5G6G

    v21 v22  
    11= 5G/NextG =
    22Team: Jeff Acevedo | Stanislav Ceman | Ryan Lin | Sreeram Mandava | Aleksa Samardzija | Nikhil Sampath | Sanskar Shah | Steve Shin | Xoua Thao
     3
     4Advisors: Ivan Seskar | N.K. Shankaranarayanan
    35== Project Objectives
    46The 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.
    … …  
    79A 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. All communication between the different functions are through the ORBIT amqp server using the RabbitMQ message-brokering software.
    810[[Image(AMQP Diagram (3).png, 500px)]]
    9 [[Image(SystemSequenceDiagram_v3.png, 500px)]]
     11[[Image(SystemSequenceDiagram_v3.png, 1000px)]]
    1012=== Topology Scenario
    1113To 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.).
    12 [[Image(TopologyStoryImage.png, 600)]]
    13 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. As detailed below, all of these functions are handled by the SMO.
     14[[Image(TopologyStoryImage.png, 1000)]]
     15
     16UEs, such as cell phones, 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 as a UE moves along the road. If one connected RU becomes out of range, the UE will connect to another in-range RU. The existence of multiple paths also ensures connectivity if one path becomes compromised. The compromised path will be shut down and the data will be transmitted through one of the alternative paths connected to that UE. Additionally, the transmission of data can be optimized among the paths. As detailed below, all of these functions are handled by the SMO.
    1417
    1518