Magma Access Gateway

Magma Access Gateway

Release Validation Report
Version:1.8_5G SA

Go to TOC Version: 1.8_5G SA Page 0 of 41

Magma Access Gateway

TABLE OF CONTENT
1. INTRODUCTION .............................................................................................................................. 5
1.1 Purpose of the Document.......................................................................................................... 5

2. ABBREVATIONS ............................................................................................................................... 5

3. SETUP ............................................................................................................................................. 6
3.1 Access Gateway Hardware ........................................................................................................ 6
3.1.1 Physical Gateways ................................................................................................................ 6
3.2 Test tools and Traffic Emulator .................................................................................................. 6
3.2.1 Test Setup Architecture ........................................................................................................ 6
3.2.2 Test Activity .......................................................................................................................... 7

4. INSTALL, UPGRADE AND VALIDATION .......................................................................................... 11

4.1 AGW BareMetal Installation .................................................................................................... 11
4.1.1 Network Type Tested ......................................................................................................... 11
4.2 AGW Upgrade .......................................................................................................................... 11
4.2.1 Upgrade Path Details .............................................................................................................. 11
4.2.2 Enable 5G features ................................................................................................................. 12
4.3 Magma Orchestrator ............................................................................................................... 13
4.4 Accessing & using Magma nms-UI (User Interface) ................................................................. 13
4.4.1 NMS-UI Validation .............................................................................................................. 16

5. FEATURE TESTING ......................................................................................................................... 18

Test Activity on Rebaca-Abot ............................................................................................................. 18
5.1 General Procedures ................................................................................................................. 19
5.1.1 AUSF-SUCI Registration ...................................................................................................... 19
5.1.2 IPV6-Support ...................................................................................................................... 22
5.1.3 Network Inititated Session Modification Support .............................................................. 23
5.1.4 Usage Reporting ................................................................................................................. 28
5.1.5 Stateless Support ................................................................................................................ 30
5.1.6 Programmable GTP extensions on PIPELINED. ................................................................... 31

6. STABILITY AND PERFORMANCE TESTING ...................................................................................... 33

6.1 Stability Testing ....................................................................................................................... 33
6.1.1 Traffic Emulator .................................................................................................................. 33
6.1.2 Test Activity on Spirent ....................................................................................................... 34
6.2 PERFORMANCE ........................................................................................................................ 35

7. TEST REPORT FROM CI PIPELINE ................................................................................................... 37

7.1 List of Abot TC running in CI .................................................................................................... 37

8. REAL EQUIPMENT TESTING-SIT............................................... ERROR! BOOKMARK NOT DEFINED.

Go to TOC Version: 1.8_5G SA Page 1 of 41

Magma Access Gateway

8.1 Test Activity on Real Device (UE) ............................................................................................. 37

8.2 List of Test Case ....................................................................................................................... 39

9. REFERENCES ................................................................................................................................. 37
LIST OF FIGURES
Figure 1: Magma 5G SA – Test Topology ............................................................................................................................. 7
Figure 2: Basic Call Flow with SUCI ....................................................................................................................................... 9
Figure 3: Call Flow with Network Initiated Session-Modification .......................................................................10
Figure 4: Curl-API showing 5G Flag Disabled .................................................................................................................12
Figure 5: Showing only 4G is UP ............................................................................................................................................12
Figure 6: Curl-API After enabling 5G ...................................................................................................................................12
Figure 7: Showing both 4G & 5G up .....................................................................................................................................12
Figure 8: Adding User .................................................................................................................................................................13
Figure 9: Subscribers Overview Page .................................................................................................................................14
Figure 10: Adding Subscribers ...............................................................................................................................................14
Figure 11: Gateway Check-Ins ................................................................................................................................................15
Figure 12: Alert Rules .................................................................................................................................................................15
Figure 13: Metrics Grafana Dashboard View ..................................................................................................................16
Figure 14: Test Activity on Abot ............................................................................................................................................19
Figure 15: SUCI Based call flow .............................................................................................................................................20
Figure 16: Curl API(Put Command) to add SUCI Profiles..........................................................................................20
Figure 17: Curl API(GET Command) to fetch SUCI Profiles .....................................................................................21
Figure 18: APN Configuration .................................................................................................................................................25
Figure 19: QoS Policy Configuration....................................................................................................................................26
Figure 20: QoS Profile Configuration ..................................................................................................................................26
Figure 21: Adding Policies to subscriber ..........................................................................................................................27
Figure 22: Output of the Policies stored in PolicyDB ..................................................................................................27
Figure 23: Grafana Usage reporting (UE Data Usage IN/OUT) for 1UE .............................................................29
Figure 24: Grafana Usage reporting (Total throughput UP/DOWN) for 1UE .................................................29
Figure 25: Grafana Usage reporting (Total throughput UP/DOWN) for Multi UE .......................................29
Figure 26: Grafana Usage reporting (Total throughput UP/DOWN) for Multi UE ........................................30
Figure 27: Commands for enabling Stateless feature .................................................................................................30
Figure 28: Different between Statefull and Stateless Mode .....................................................................................31
Figure 29: Programmable GTP Header Call Flow .........................................................................................................32
Figure 30: High level block diagram for the emulated setup for a NAT setup ................................................33
Figure 31: High level block diagram for the emulated setup for a DHCP setup .............................................34
Figure 32: Test Activity on Spirent ......................................................................................................................................35
Figure 33: Spirent GUI 400Mbps traffic Graph...............................................................................................................36
Figure 34: Test Activity on Real Device .............................................................................................................................38
Figure 35: UE in Aeroplan mode ...........................................................................................................................................38
Figure 36: UE with 5G Signal Detected...............................................................................................................................39
Figure 37: Traffic sent by UE after PDU Establishment .............................................................................................39
LIST OF TABLES
Table 1: Physical Gateway Specifications ........................................................................................................................... 6
Table 2: AGW Upgrade actions and Commands ............................................................................................................11
Table 3: Access Gateway upgrade ........................................................................................................................................11
Table 4: NMS Validation ............................................................................................................................................................18
Table 5: Software Build info - 1.8.0-1663094999-49ed2e69 .................................................................................22

Go to TOC Version: 1.8_5G SA Page 2 of 41

Magma Access Gateway

Table 6: List of IPV6 Testcases ...............................................................................................................................................23

Table 7: List of Network Initiated Session Modification Test cases.....................................................................24
Table 8: TC tested as per QoS-Support...............................................................................................................................28
Table 9: Different Combinations of Policies Tested .....................................................................................................28
Table 10: Stateless Feature – Test Performed on Spirent.........................................................................................31
Table 11: Programable GTP Extension Header ..............................................................................................................32
Table 12: Performance ...............................................................................................................................................................35
Table 13: Performance with Description & Duration .................................................................................................36
Table 14: CI/CD Test summary report ...............................................................................................................................37
Table 15: Real Equipment Testing .......................................................................................................................................40

Go to TOC Version: 1.8_5G SA Page 3 of 41

Magma Access Gateway

Version Information
Title Magma Access Gateway
Document Ver. No. V 1.8_5G-SA
Approved By
Drafted by
Doc. Classification

Version History
Version # Date Author(s) Approved by Description
Parthiban
1.0 4-July-2022 Nalliamudali Initial Report
/ Neelima K
Parthiban
2.0 15-Sep-2022 Nalliamudali Final Report
/ Neelima K

Go to TOC Version: 1.8_5G SA Page 4 of 41

Magma Access Gateway

1. INTRODUCTION

1.1 P URPOSE OF THE D OCUMENT

The purpose of this document is to enable 5G in the magma 5G Core and validate 5G Extended
Features in magma-core using different testing tools (Rebaca ABot, Spirent, etc.,). It also has the test
reports from each tool.

2. ABBREVATIONS

# Abbreviations Expansions
1 AGW Access Gateway
2 UE User Equipment
3 BW Bandwidth
4 SUCI Subscription Concealed Identifier
5 GUTI Globally Unique Temporary ID
6 SCTP Stream Control Transmission Protocol
7 NGAP NG Application Protocol
8 NMS Network Management Station
9 NAS Non-access stratum
110 AMF Access and Mobility Management Function
12 AN Access Network
13 RRC Radio Resource Control
14 3GPP 3rd Generation Partnership Project
15 CM Centimeter wave
16 RAN Radio Access Network
17 NG-RAN NG Radio Access Network
18 5GMM 5G Mobility Management
19 PDU Protocol Data Unit
20 TC Test Cases
21 SMF Session Management Function
22 APN Access Point Name
23 DNN Data Network Name
24 QOS Quality of Service
25 NAT Network Address Translation

Go to TOC Version: 1.8_5G SA Page 5 of 41

Magma Access Gateway

3. SETUP

Here it shows the Test SETUP for Access Gateway where the main services/procedures are
validated are done.

3.1 A CCESS G ATEWAY H ARDWARE

➢ Below is the list of Access Gateway Hardware.

3.1.1 PHYSICAL GATEWAYS

ITEM DESCRIPTION
CPU X86_Intel_4 Cores_Speed 1.91 GHz
RAM 8 GB
Storage 60.00 GB
Table 1: Physical Gateway Specifications

3.2 T EST TOOLS AND T RAFFIC E MULATOR

➢ Abot UE and gNb simulators along with automation framework to test functional/features of
Magma 5GC.
➢ Spirent is used for functional and non-functional testing.

3.2.1 TEST SETUP ARCHITECTURE

➢ Below diagram represents the Magma 5G SA test topology. Here Magma AGW is connected with
AWS public cloud orchestrator (Hosted by Wavelabs).
➢ From Orchestrator the information is saved in subscriber DB of Magma 5GC. AMF gets the
information from subscriber DB and give to SMF.

Go to TOC Version: 1.8_5G SA Page 6 of 41

Magma Access Gateway

Figure 1: Magma 5G SA – Test Topology

➢ UPF takes care of all data plane and allows packet processing & traffic aggregation which is to be
performed closer to the network edge, increasing bandwidth efficiencies while reducing
network load.
➢ AMF receives all connection and session related information from the UE, but is responsible only
for handling connection and mobility management tasks.
➢ Once the registration is completed, PDU establishment request comes in and internally AMF
sends the request to SMF and SMF fetches the APN or Policy information.
➢ SMF also performs the Session-Modification Trigger whenever there is update in the Qos-
Policies configured. As of now, this is tested using CLI command.
➢ Once the sessions are up or it is successful, SMF sends the session related information to UPF
and traffic is triggered over the session.

3.2.2 TEST ACTIVITY

➢ Below are the different call flows that are supported in Magma 5GC got released in 1.7.
• Basic Call Flow with SUCI
• Basic Call Flow with GUTI
• Active/Idle mode tests
• PDU-Establishment and PDU-Release Procedures
• De-Registration Procedures
Note: For detailed information about above procedure please refer 1.7 Release document.
➢ Below are the add on features in 1.8 release.

Go to TOC Version: 1.8_5G SA Page 7 of 41

Magma Access Gateway

• SUCI Registration with Encryption.

• Network Initiated Session Modification.
• PDU-Session – Ipv4, IPv6 and IPv4v6 support.
• Usage Report.
• Stateless Support.
• Programmable GTP extensions on Pipelined.
• Qos – Profiles Support in 5G
3.2.2.1 SUCI Registration with Encryption
• SUCI allows SUPI to be signaled without exposing the identity of the user.
• When the testcase is triggered, it initiates an INITIAL_UE_MESSAGE that is received
from UE to AMF, which is for connection establishment. Now a new registration
request comes in and it is processed internally.
• During the registration procedure, internally AMF requested AUSF(Subscriber-db) to
decrypt the MSIN .
• Once the MSIN is identified by hiding the user identity, rest of the sub-procedures will
be accomplished.
• Here we are supporting 2 types of encryption algorithms: Profile-A and Profile-B.
• For decryption we are using ECIES algorithm.
• Once the Authentication Request & Response and Security mode is done, user sends
the context request to gNodeB and accept the UE, so that UE moves to registered
connected mode. i.e., UE registration is completed.
• After completion of the registration, the PDU-Establishment is triggered.
• PDU-Establishment request comes from UE and PDUSessionResourceSetupRequest,
DL NAS transport and PDU session establishment accept messages are sent by AMF.
Once this is completed the traffic is triggered.
o PDUSessionResourceSetupRequest is for gnodeb to allocate the resources for
the UE-Context.
o PDUSessionResourceSetupResponse is the response from gnodeb, with this
PDU-Establishment is finished and traffic is started.
• Once the traffic session is completed, the PDU-Release is done.
• After completion of PDU-Release, the De-Registration is done.

Go to TOC Version: 1.8_5G SA Page 8 of 41

Magma Access Gateway

Figure 2: Basic Call Flow with SUCI

3.2.2.2 GUTI Based registration with SUCI-Encryption

• When the testcase is triggered, it initiates an INITIAL_UE_MESSAGE that is received
from UE to AMF, which is for connection establishment. Now a new registration
request comes in and it is processed internally.
• Here during the registration procedure, internally Identity mode, Authentication and
Security mode commands are triggered.
• Here in Identity-Response if UE is sending a encrypted info of UE identity , AMF
internally request AUSF for decryption and then triggers follow-up procedures.
• Once the Identity Request & Response, Authentication Request & Response and
Security mode is done, user sends the context request to gNodeB and accept the UE,
so that UE moves to registered connected mode. i.e., UE registration is completed.
• After completion of the registration, the PDU-Establishment is triggered.
• PDU-Establishment request comes from UE and PDUSessionResourceSetupRequest,
DL NAS transport and PDU session establishment accept messages are sent by AMF.
Once this is completed the traffic is triggered.
o PDUSessionResourceSetupRequest is for gnodeb to allocate the resources for
the UE-Context.
o PDUSessionResourceSetupResponse is the response from gnodeb, with this
PDU-Establishment is finished and traffic is started.
• Once the traffic session is completed, the PDU-Release is done.
• After completion of PDU-Release, the De-Registration is done.

Go to TOC Version: 1.8_5G SA Page 9 of 41

Magma Access Gateway

Figure 2: Basic Call Flow with GUTI

3.2.2.3 Network Initiated PDU-Session Modification

• PDU-Session modification is an enhancement in the magma-5G SA.
• After PDU-Establishment, if the service provider wants to upgrade/degrade the Qos-
policies applied for a given session for a given user, will update the qos-policy info in
PCF-Module which will be communicated to SMF via FEG-Relay and Orchestrator.
• Currently in Magma, it is handled by simple CLI command which updates the policy
changes to SMF for a given Session-id specific to SMF(Sessiond).
• Once a trigger comes to the session about the session parameter changes, Sessiond
notify the same to UE/gNb via AMF(mme) .
PDU-Session-Modification Request and Command will be triggered here.
• Here, it can be a PDU-Session-Modification-Complete/Reject message from UE.
• If it is PDU-Accept from UE and PDU-Modification-ResourceSetupRespose message
from gNB , AMF notifies the same to Sessiond. Sessiond will apply the modified
policy on the session and notifies the same to pipelined.
• From now traffic tunning will happen as per new policy applied.

Figure 3: Call Flow with Network Initiated Session-Modification

Go to TOC Version: 1.8_5G SA Page 10 of 41

Magma Access Gateway

4. INSTALL, UPGRADE AND VALIDATION

4.1 AGW B ARE M ETAL I NSTALLATION

Step.1 Install AGW V1.8

Step.2 Download and run using the below URL.
Wgethttps://raw.githubusercontent.com/magma/magma/v1.8/lte/gateway/deploy/agw_ins
tall_ubuntu.sh

4.1.1 NETWORK TYPE TESTED

➢ NAT (Network Address Translation) is a way to map multiple local private addresses to a public
address before transferring the information. Organization which wants multiple devices to
employ a single IP address uses the NAT (As like home routers).
➢ Basic Non-NAT testing is done and extensive testing is in progress.

4.2 AGW U PGRADE

4.2.1 UPGRADE PATH DETAILS

ACTIONS COMMANDS USED
To Check the Installed version apt list –installed | grep magma

To check the latest package in the master-ci apt-cache madison magma

To Upgrade/Update to the latest Master Build sudo apt update
sudo apt-get install magma
To Update to specific Version in Master-CI sudo apt-get install magma=Version_Number

Table 2: AGW Upgrade actions and Commands

➢ Access Gateway upgraded path to V1.8.

➢ We are having Orc8r with V1.8 Version.

Note: ryu patch must be installed after the installation of v1.8 magma AGW.
https://artifactory.magmacore.org/artifactory/debian-test/pool/focal-1.8.0/python3-
ryu_4.34_all.deb

INITIAL VERSION UPGRADED VERSION UPGRADE LOGS & VERIFICATION

1.6.0(4G) 1.8.0(4G and 5G) Click Here

1.6.1(4G) 1.8.0(4G and 5G) Click Here

1.7.0(4G and 5G) 1.8.0(4G and 5G) Click Here
Table 3: Access Gateway upgrade

Go to TOC Version: 1.8_5G SA Page 11 of 41

Magma Access Gateway

4.2.2 ENABLE 5G FEATURES

➢ In below screen shot the Curl API shows, enable 5G feature flag as “False” and in this API
the 5G features can be enabled.

Figure 4: Curl-API showing 5G Flag Disabled

➢ Below is the sctp port output where it shows only 4G, i.e., only 4G port (36412) is up.

Figure 5: Showing only 4G is UP

➢ To enable 5G features, user must enable 5G feature flag as “True”, which gets reflected in the
config file of AGW via orchestrator (5G AGW comes up with 5G ports).
➢ In below screen shot the Curl API shows enable 5G feature flag as “True” and in this API the
5G features are enabled.

Figure 6: Curl-API After enabling 5G

➢ Below is the sctp ports output which shows both 4G and 5G ports are up. (36412 for 4G and
38412 for 5G)

Figure 7: Showing both 4G & 5G up

Go to TOC Version: 1.8_5G SA Page 12 of 41

Magma Access Gateway

4.3 M AGMA O RCHESTRATOR

➢ Magma's Orchestrator is a centralized controller for a set of networks. Orchestrator handles the
control plane for various types of gateways in Magma. Orchestrator functionality is composed of
two primary components.
• A standardized, vendor-agnostic northbound REST API which exposes configuration
and metrics for network devices
• A southbound interface which applies device configuration and reports device status
➢ Click here to know more about Orchestrator.
➢ Click here for orchestrator installation guide.

4.4 A CCESSING & USING M AGMA NMS -UI (U SER I NTERFACE )

➢ Magma NMS provides an enterprise grade GUI for provisioning and operating magma based
networks. It enables operators to create and manage:
• Organizations
• Networks
• Gateways and eNodeBs
• Subscribers
• Policies and APNs
Step.1 Add Users.
✓ New users to NMS can be added or edited through the admin page.
✓ Users can be configured as a superuser/user/readonly user.

Figure 8: Adding User

Step.2 Subscriber configuration.

✓ The Subscriber Overview page contains a table listing all subscribers in the network.
✓ Subscriber configuration in the overview page provides the ability to do bulk
provisioning of subscribers by either entering the details manually or uploading them
through a subscriber .csv file.
✓ Clicking on the 'Add subscriber' button in the subscriber overview page opens the bulk
subscriber configuration page.

Go to TOC Version: 1.8_5G SA Page 13 of 41

Magma Access Gateway

Figure 9: Subscribers Overview Page

Figure 10: Adding Subscribers

Step.3 Check-in Gateway.

✓ Gateway overview table with a selector is to view either status or upgrade of the
gateways in the network.
✓ Click on Add New button to add a new access gateway in the network.

Go to TOC Version: 1.8_5G SA Page 14 of 41

Magma Access Gateway

Figure 11: Gateway Check-Ins

Step.4 Sync predefined alerts.

✓ Magma NMS comes loaded with some default set of alert rules. These default rules are
not configured automatically. If an operator chooses to use these default rules, then they
can do it by clicking on “Sync Predefined Alerts” button in Alert rule configuration tab.

Figure 12: Alert Rules

Step.5 Metrics-Grafana dashboard.

✓ Metrics Grafana dashboards contain dropdown selectors to choose which network(s)
and gateway(s) user wants to look at.
✓ In Grafana, user can look at any collection of networks or gateways which their
organization has access to it.

Go to TOC Version: 1.8_5G SA Page 15 of 41

Magma Access Gateway

Figure 13: Metrics Grafana Dashboard View

4.4.1 NMS-UI VALIDATION

➢ NMS (Network Management Station) is a part of Orchestrator, and it is a multitenancy where
user can add organization and the network.
TESTCASE TEST SCENARIO RESULT
ID
TC1 NMS - Create an organization Pass

TC2 NMS - Administrative tools -Create a user Pass

TC3 NMS - Administrative tools -Audit log Pass

TC4 NMS - Administrative tools -Create a network Pass

TC5 NMS - Network -Create a network Pass

TC6 NMS - Network -Edit network Pass

TC7 NMS - Network -Edit Epc Pass

TC8 NMS - Network -Edit Ran Pass

TC9 NMS - Equipment - Gateway -Create a gateway Pass

TC10 NMS - Equipment – Gateway-Create an eNodeB Pass

TC11 NMS - Equipment – Gateway-Create a gatewaypool Pass

TC12 NMS - Subscriber -Create a subscriber Pass

TC13 NMS - Subscriber -Configure subscriber Pass

TC14 NMS - Subscriber -Session subscriber Pass

TC15 NMS - Subscriber -Edit a subscriber Pass

Go to TOC Version: 1.8_5G SA Page 16 of 41

Magma Access Gateway

TC16 NMS - Subscriber -Edit a traffic policy Pass

TC17 NMS - Subscriber -Edit an APN static IPs NA

TC18 NMS - Subscriber-Overview-Overview of subscribers,Status, Datausage Pass

TC19 NMS - Subscriber-Overview-Overview of subscribers Pass

TC20 NMS - Subscriber-Overview-Status Pass

TC21 NMS - Subscriber-Overview-Datausage Pass

TC22 NMS - Subscriber-Event-Create an Event Pass

TC23 NMS - Traffic – Policies-Create a profile Pass

TC24 NMS - Traffic - Policies -Create a policy Pass

TC25 NMS - Traffic - Policies -Create a Rating group Pass

TC26 NMS - Traffic – APNs-Create an APN Pass

TC27 NMS - Traffic – APNs-Modify an APN Pass

TC28 NMS - Network -Modify a network Pass

TC29 NMS - Network -Enable NAT Pass

TC30 NMS - Network -Enable DHCP Pass

TC31 NMS - Network -Enable Static IP NA

TC32 NMS - Network -Enable policy Enforcement NA

TC33 NMS - Equipment - Gateway -Modify a gateway Pass

TC34 NMS - Equipment -Gateway overview-Overview of Gateway Pass

TC35 NMS - Equipment -Gateway status-Enable event aggregation Pass

TC36 NMS - Equipment -Gateway status-Enable log aggregation Pass

TC37 NMS - Equipment – eNodeB-Add a managed eNodeB Pass

TC38 NMS - Equipment - Gateway Configure-Edit Aggregation Pass

TC39 NMS - Equipment - Gateway Configure-Edit EPC Pass

TC40 NMS - Equipment - Gateway Configure-Edit RAN Pass

TC41 NMS - Equipment - Gateway Configure-Edit Header Enrichment Pass

TC42 NMS - Equipment - Gateway Configure-Edit Dynamic services Pass

TC43 NMS - Call Tracing -Create call trace Pass

TC44 NMS - Call Tracing -Download call trace Pass

TC45 NMS - Metrics -Check Metrics Pass

Go to TOC Version: 1.8_5G SA Page 17 of 41

Magma Access Gateway

TC46 NMS - Metrics -Check Grafana Pass

TC47 NMS – Metrics-Configure Metric Explorer Pass

TC48 NMS - Alerts -Configure Alerts Pass

TC49 NMS - Alerts -View Alerts Pass

TC50 NMS - Alerts Rules-Add Alert rules Pass

TC51 NMS - Alerts - receivers -Configure Alert receivers Pass

TC52 NMS - Alerts -Sync Predefined Alerts Pass

Table 4: NMS Validation

Note: Click here to find the test results of UI Pages.

5. FEATURE TESTING

➢ Feature Testing is to explain all procedures and sub procedures that are tested as part of Magma
5G SA- V1.8 release.

T EST A CTIVITY ON R EBACA -A BOT

➢ After installing Abot core, user must configure the Gnb, AGW IP ports and Abot Analytic IP.
➢ Have Access Gateway installed with V1.7 or upgrade it from the older version to V1.8 (Refer
section 4.2 for AGW Upgrade)
➢ Rebaca’s Abot is integrated with the magma CICD which automatically triggers the test run for
every single built that coming in and V1.8 is exclusively tested using the Abot test tool.
➢ The feature files are executed as per below steps.
Step.1 Test bed comes up.
Step.2 Feature file execution is started
Step.3 Test bed comes down
Step.4 Feature file execution is completed. (All the feature files execution are completed)
➢ After executing the feature file, in few seconds logs and PCAPS are generated in the artefacts.
➢ User can download PCAPS and the Logs from the Artefacts.

Go to TOC Version: 1.8_5G SA Page 18 of 41

Magma Access Gateway

Figure 14: Test Activity on Abot

5.1 G ENERAL P ROCEDURES

➢ General Procedures includes:

• Registration with SUPI/GUTI
• PDU-Establishment and PDU-Release
• Connection Management Procedures.
➢ Some of Extended procedures, that includes:
• Multi-PDU session support
• DNN support
• PDU-Rejection cases
Note: For above procedures are covered as part of Magma-5G SA 1.7 Alpha release -Test Report
document.

5.1.1 AUSF-SUCI REGISTRATION

➢ SUCI - is a privacy preserving identifier containing the concealed SUPI.
➢ ECIES-based protection scheme is used for de-concealing the MSIN.
➢ SUCI Based call flow

Go to TOC Version: 1.8_5G SA Page 19 of 41

Magma Access Gateway

Figure 15: SUCI Based call flow

S WAGGER API I NFO :

➢ Curl API to add SUCI Profiles from Swagger:

Figure 16: Curl API(Put Command) to add SUCI Profiles

➢ Curl API to fetch SUCI Profiles from Swagger:

Go to TOC Version: 1.8_5G SA Page 20 of 41

Magma Access Gateway

Figure 17: Curl API(GET Command) to fetch SUCI Profiles

Software Build info - 1.8.0-1663094999-49ed2e69

AUSF-SUCI Registration – Test Execution on Abot

Test ID Test case name Result

TC_AUSF_001 Verify_SUCI_REG_with_ProfileA FAIL

TC_AUSF_002 Verify_SUCI_REG_with_ProfileB FAIL

TC_AUSF_003 Verify_SUCI_REG_with_ProfileA_DeRegister_and_RegWith_ProfileB FAIL

TC_AUSF_003a Verify_SUCI_REG_with_ProfileB_DeRegister_and_RegWith_ProfileA FAIL

TC_AUSF_004 Verify_SUCI_REG_with_ProfileA_with_InvalidPublicKey PASS
TC_AUSF_005 Verify_SUCI_REG_with_ProfileA_with_InvalidLengthPublicKey PASS
TC_AUSF_006 Verify_SUCI_REG_with_ProfileA_with_InvalidPriveKey PASS
TC_AUSF_007 Verify_SUCI_REG_with_ProfileA_with_InvalidLengthPrivateKey PASS

TC_AUSF_008 Verify_SUCI_REG_with_ProfileA_with_BothKeys_Invalid PASS

TC_AUSF_009 Verify_SUCI_REG_with_ProfileA_ScheameIdentifier PASS

TC_AUSF_010 Verify_SUCI_REG_with_ProfileA_with_Invalid_HomeNetworkIdentifier. PASS

TC_AUSF_011 Verify_SUCI_REG_with_ProfileB_with_InvalidPublicKey PASS
TC_AUSF_012 Verify_SUCI_REG_with_ProfileB_with_InvalidLengthPublicKey PASS
TC_AUSF_013 Verify_SUCI_REG_with_ProfileB_with_InvalidPriveKey PASS

Go to TOC Version: 1.8_5G SA Page 21 of 41

Magma Access Gateway

TC_AUSF_014 Verify_SUCI_REG_with_ProfileB_with_InvalidLengthPrivateKey PASS

TC_AUSF_015 Verify_SUCI_REG_with_ProfileB_with_BothKeys_Invalid PASS

TC_AUSF_016 Verify_SUCI_REG_with_ProfileB_ScheameIdentifier PASS

TC_AUSF_017 Verify_SUCI_REG_with_ProfileB_with_Invalid_HomeNetworkIdentifier. PASS

TC_AUSF_018 Verify_SUCI_REG_with_ProfileB_with_Invalid_HomeNetworkIdentifier_Beyond255 PASS

TC_AUSF_019 Verify_SUCI_REG_with_ProfileA_with_Invalid_HomeNetworkIdentifier_Beyond255 PASS

TC_AUSF_020 Verify_Identity_Response(IN_GUTI)_with_SUCI_Profile_A FAIL

TC_AUSF_021 Verify_Identity_Response(IN_GUTI)_with_SUCI_Profile_B FAIL

TC_AUSF_022 Verify_SUCI_REG_with_ProfileA_ ciphertext_10len PASS

TC_AUSF_023 Verify_SUCI_REG_with_ProfileB_ ciphertext_10len PASS

TC_AUSF_024 Verify_Identity_Response(IN_GUTI)_with_SUCI_Profile_A _ ciphertext_10len FAIL

TC_AUSF_025 Verify_Identity_Response(IN_GUTI)_with_SUCI_Profile_A _ ciphertext_10len FAIL

Table 5: Software Build info - 1.8.0-1663094999-49ed2e69

Note1: The configured Profiles are not persistent. When AGW get rebooted , user must save the profiles
again in the Subscriber-db.
Note2: All the above test cases are automated: Currently test tool supports Profile-A and Profile-B
configurations manually.

5.1.2 IPV6-SUPPORT
Magma 5G System supports following three PDU Session types to cover different potential use
cases:

• IPv4 PDU Session

• IPv6 PDU Session
• Dual-Stack IPv4v6
The IPv6 pool allocation changes allow the assignment of a block of IPv6 prefixes for user devices.
This feature also enables IPv6 static allocation to enable the assignment of an IPv6 prefix to an IMSI
in subscriberDB. With this new implementation, Magma supports IPv4, IPv4v6, and IPv6 APN types.

Note1: IPV6 support is given only in the user-plane . Still control plane and GTP packets are carried
over IPV4
Note2: Magma doesn’t support Ethernet PDU Session and Unstructured PDU Session

Software Build info - 1.8.0-1663094999-49ed2e69

Go to TOC Version: 1.8_5G SA Page 22 of 41

Magma Access Gateway

IPV6(Control Plane Tested Using Abot)

Test ID Test case name Automation Status Result

MGM-5GSA-FUNC-TC054 Verify 5G UE IPv6 Automated Pass

Automated
MGM-5GSA-FUNC-TC054 Verify 5G UE IPv6_Default as DNN Pass
Automated
MGM-5GSA-FUNC-TC053 Verify 5G UE IPv4v6 (Dual Stack) Pass

Verify 5G UE IPv4 only and Ipv6 only in two diff Automated

MGM-5GSA-FUNC-TC052 pdu sessions Pass
IPv6_Verify_Idle_and_Active_Mode_transition_with Automated
MGM-5GSA-FUNC-TC071 _Multi_PDU_session Pass

IPv6_UE Idle Mode Support (Service Request - MO Automated

Data) + PDU session
MGM-5GSA-FUNC-TC072 Pass

Test Case for Data Plane on Spirent

Automated
TC12 TC12_IPV6Support_WithTraffic Fail
Automated
TC13 TC13_IPV4V6Support_WithTraffic Fail

TC14_Multi_Session_IPV4_IPV6_IPV4_IPV6_Traffic_ Automated
TC14 Dereg Fail
Table 6: List of IPV6 Testcases

5.1.3 NETWORK INITITATED SESSION MODIFICATION SUPPORT

➢ When using local policydb and when static rules are enabled or disabled,
Npcf_SMPolicyControl_UpdateNotify is sent to the SessionD to install or remove the static
rules.
➢ Session modification can be triggered by adding, delete and modify a policy.
➢ In magma in current release only adding and deleting a policy is supported.
➢ As of now for PCF functionality of triggering session modification is done by sessiond Stub-CLI
command developed for testing purpose.
➢ Below are the list of TC designed for testing:

Software Build info - 1.8.0-1663094999-49ed2e69

Network Initiated Session Modification – Tested with Spirent

Test ID Test case name Result

Automation Status

Go to TOC Version: 1.8_5G SA Page 23 of 41

Magma Access Gateway

TC_NW_INIT_S Verify_NW_Init_SessModif_with_SingleSession_SUCI
es_Mod_01 _Based Automated Pass
TC_NW_INIT_S Verify_NW_Init_SessModif_with_SingleSession_GUT
es_Mod_02 I_Based Manual Pass

TC_NW_INIT_S Verify_NW_Init_MultipleTimesWithSamePolicy_Ses Manual

es_Mod_03 sModif_with_SingleSession_SUCI_Based Pass

TC_NW_INIT_S Verify_NW_Init_MultipleTimes_WithDiffPolicy_Sess Automated

es_Mod_04 Modif_with_SingleSession_SUCI_Based Pass

TC_NW_INIT_S Verify_NW_Init_SessModif_with_InvalidSessionID_S Automated

es_Mod_05 UCI_Based Pass

TC_NW_INIT_S Verify_NW_Init_SessModif_with_InvalidAPN_SUCI_ Automated

es_Mod_06 Based Pass

TC_NW_INIT_S Verify_NW_Init_SessModif_With_MultiplePDU_Sessi Automated

es_Mod_07 ons Pass
TC_NW_INIT_S Verify_NW_Init_SessModif_With_MultiplePDU_Sessi
es_Mod_08 ons_MultiSession_Modification Manual Pass
Verify_NW_Init_SessModif_With_MultiplePDUSessi
TC_NW_INIT_S ons_MultiSession_Modification_ValidInvalid_sessio Manual Pass
es_Mod_09 n

TC_NW_INIT_S Verify_NW_Init_SessModif_Before_PDU_Session_Est Manual

es_Mod_10 ablishment Pass
TC_NW_INIT_S
es_Mod_11 Verify UE deny Session Modify Reject Case Automated Fail

TC_NW_INIT_S Verify the session modification with deleting a Automated

es_Mod_12 policy Fail
Table 7: List of Network Initiated Session Modification Test cases

QOS-SUPPORT
➢ Qos in Magma supports different Policy enforcement on the user traffic.
➢ AMF exchanges the various policy parameters to UE and gNb during PDU-Establishment.
➢ Below are the various Qos-Parameters that supported in Magma.
• QFI and 5QI values
• Priority
• UL/DL Session AMBRs
• ARP – Allocation and Retention Priorities.
• Pre-emption Capability and Pre-emption Vulnerability Parameters
➢ By default when PDU-Session is up, if there is no Qos-Policy applied for a given subscriber,
Sessiond will pick the above specified parameters from the APN that a UE gets subscribed.

Go to TOC Version: 1.8_5G SA Page 24 of 41

Magma Access Gateway

➢ If there is any policy applied for a given subscriber, Sessiond will apply respective policies on the
session and the information is shared to UE in PDU-Establishment-Accept message and the same
is shared to gNB as part of PDUSessionResourceSetupRequestTransfer Message
➢ And Pipelined use to tune the traffic flow according to the policies and APN AMBRs that are
subscribed by a given subscriber.
➢ And Qos Policies configurations also supports flow match criteria as per 3GPP.
➢ If there is a flow restriction , in a particular Qos-Policy , fast path enforce the same and transfers
the traffic as per the flow controls.
➢ Below are different flow controls supported in Magma.
• Match Criteria – Allow/Deny
• Traffic types – IP, UDP ,TCP and ICMP
• With Specific Source and Destination IP and Port.
➢ Below are the configurations from NMS for Qos Policies and Profiles.
• Configure the APN from the NMS Traffic Page

Figure 18: APN Configuration

• Configure the QOS-Policy from NMS Traffic Page

Go to TOC Version: 1.8_5G SA Page 25 of 41

Magma Access Gateway

Figure 19: QoS Policy Configuration

• Configure the QOS-Profile from NMS Traffic Page

Figure 20: QoS Profile Configuration

➢ Appling a policy on the Subscriber

Go to TOC Version: 1.8_5G SA Page 26 of 41

Magma Access Gateway

Figure 21: Adding Policies to subscriber

➢ Command to check the policy information in policed

Figure 22: Output of the Policies stored in PolicyDB

➢ Below are TC tested as per Qos-Support

Software Build info - 1.8.0-1663094999-49ed2e69

Qos-Support – Test Performed on Spirent
Test ID Test case name Result
Qos_TC01 Default_APN_Profile PASS
Qos_TC02 Qos_With_Flow_IPPackets_Deny PASS

Go to TOC Version: 1.8_5G SA Page 27 of 41

Magma Access Gateway

Qos_TC03 Qos_With_Flow_TCP_Packets_Deny PASS

Qos_TC04 Qos_With_Flow_UDP_Packets_Deny PASS
Qos_TC05 Qos_With_Flow_All_PacketsTypes_Deny PASS
Qos_TC06 Qos_With_MultipleQFI_MULTIPLESessions PASS
Qos_TC07 Qos_With_SingleSession_MultiPlePolicies FAIL
Qos_TC08 Qos_With_MultiSession_MultiPlePolicies FAIL
Qos_TC09 Qos_With_MultiSession_MultiPolicies(APN to Policy Mapping) FAIL
Table 8: TC tested as per QoS-Support

➢ Different Combinations of Policies Tested

POLICY FLOW1 FLOW2

NUMBER
action direction protocol action direction protocol Result
policy1 permit downlink ip permit uplink ip pass
policy2 permit uplink UDP permit downlink ip Pass
policy3 permit uplink TCP permit downlink TCP Pass
policy4 permit uplink icmp permit downlink ICMP pass
policy5 permit uplink ip deny downlink ip pass
policy6 deny uplink UDP permit downlink UDP Pass
policy7 permit uplink TCP deny downlink TCP Pass
policy8 deny uplink ICMP permit downlink ICMP Pass
Policy9 deny uplink IP permit downlink IP Pass
policy10 deny downlink UDP permit uplink UDP Pass
policy11 deny downlink TCP permit uplink TCP Pass
policy12 deny uplink ICMP permit downlink ICMP Pass
policy13 permit uplink ip deny downlink ip Pass
policy14 permit downlink UDP permit uplink UDP Pass
policy15 permit downlink TCP permit uplink TCP Pass
policy16 permit downlink ICMP Permit uplink ICMP Pass
Table 9: Different Combinations of Policies Tested

5.1.4 USAGE REPORTING

➢ Magma currently supports basic usage metering. This allows for real-time monitoring of data
usage at various levels in the network in Grafana Page.
• Per subscriber
• Per Network
• Per Gateway.
➢ Grafana provides a powerful, configurable, and user-friendly dashboarding solution. Any users
within an organization can create and edit custom timeseries dashboards that will be visible to
all other users in their organization. An important detail is that Grafana access is limited only to
users in an organization with the "Super-User" title
Verified Usage reporting with Single UE and Multiple UE with different traffic flow.

Go to TOC Version: 1.8_5G SA Page 28 of 41

Magma Access Gateway

➢ Below are few scenarios with screen shots

Figure 23: Grafana Usage reporting (UE Data Usage IN/OUT) for 1UE

Figure 24: Grafana Usage reporting (Total throughput UP/DOWN) for 1UE

Figure 25: Grafana Usage reporting (Total throughput UP/DOWN) for Multi UE

Go to TOC Version: 1.8_5G SA Page 29 of 41

Magma Access Gateway

Figure 26: Grafana Usage reporting (Total throughput UP/DOWN) for Multi UE

5.1.5 STATELESS SUPPORT

➢ Stateless feature provides failure recovery mechanism by storing user data in a persistent
storage.
➢ On occurrence of a failure, AGW will retrieve the UE data from the persistent storage, a partial
service interruption may occur, and once the AGW is respawned then registered users can
access the service without having a fresh registration.
Below are commands for enabling Stateless feature in Magma:

Figure 27: Commands for enabling Stateless feature

How Stateless Feature Works

➢ The MME will sync UE Registration and Session Management data into Persistent
➢ Storage(Redis Database) for pre-defined trigger points.
➢ Incase of any MME failure/restart, MME will fetch UE specific data from Redis Database.

Go to TOC Version: 1.8_5G SA Page 30 of 41

Magma Access Gateway

Figure 28: Different between Statefull and Stateless Mode

Software Build info - 1.8.0-1663094999-49ed2e69

Stateless Feature – Test Performed on Spirent
Test
Test case name Result
ID
TC_01 Verify all the Registered UEs are stable after a service restart. PASS
Verify all the Registered UEs and PDU-Sessions established are stable after a
TC_02 service restart. PASS
TC_03 Verify_PDU_Sessins_Stability_after_Sessiond_Restart Fail
TC_04 Verify_PDU_Sessins_Stability_after_mme_Restart Fail
TC_06 Verify_Traffic_flow_for_single_UE_after_Service_Restart Fail
TC_07 Verify_Traffic_flow_for_Multiple_UE_after_Service_Restart Fail
Table 10: Stateless Feature – Test Performed on Spirent

5.1.6 PROGRAMMABLE GTP EXTENSIONS ON PIPELINED.

➢ This feature provides a flexible QFI configuration for a given PDU-Session over the gtp-tunnel.
➢ With this feature service provider can configure different QFI values in QOS-Policies and bind to
the subscriber.
➢ Once the PDU session is up. Pipelined will enforce the traffic flow according to policy assigned
and respective QFI will get reflected in the GTP header.
➢ UL/DL Traffic with matched flow control will get forwarded over the gtp-tunnel. Other traffic
which is not matching configured Qos-Rules will get dropped.

Go to TOC Version: 1.8_5G SA Page 31 of 41

Magma Access Gateway

Call Flows:

Figure 29: Programmable GTP Header Call Flow

Test Cases Execute for the feature:

Software Build info - 1.8.0-1663094999-49ed2e69

Programable GTP Extension Header
Test ID Test case name Result
TC_01 Verify QFI value in gtp header in the UL/DL traffic. (Set QFI=9) PASS
TC_02 Verify QFI value in gtp header in the UL/DL traffic. (Set QFI=6) FAIL
Verify QFI value in gtp header in the UL/DL traffic when there is a
TC_03 policy applied for a user.(QFI=9) PASS
Verify QFI value in gtp header in the UL/DL traffic in case of
TC_04 multi-session(QFI=9) PASS
Verify QFI value in gtp header in the UL/DL traffic in case of single
TC_05 -session Multiple Policies FAIL

TC_06 Verify_Traffic_drop_when_Mismatch_In_QFI PASS

Table 11: Programable GTP Extension Header

Note: QFI value validation as part of GTP extension header is done as part of QoS testing.

Note: Click here to find the test results and the debug logs of the above test cases for all features.

Go to TOC Version: 1.8_5G SA Page 32 of 41

Magma Access Gateway

6. STABILITY AND PERFORMANCE TESTING

6.1 S TABILITY T ESTING

➢ Stability Testing is a type of Software Testing to check the quality and behavior of the software
in different environmental parameters. It is defined as the ability of the product to continue to
function over time without failure. Here, the test runs with maximum number of UEs, with
maximum session and supported throughput for long duration.

6.1.1 TRAFFIC EMULATOR

➢ Traffic Emulator is a tool where stress data is validated and reported with server functionalities.
➢ Below diagram is Spirent setup where scale test is performed. Here the Emulated UEs, Emulated
server and Emulated gNodeBs are the Spirent Landslide 5G which is connected with the lab
network, and the lab network is connected with Magma Access Gateway.
➢ Eth1 interface is connected with AGW and Eth0 is connected with Orchestrator.
➢ From Eth0 to lab network traffic signals are sent, this interface is used for GTP interface. (GTP is
the UPF path)
➢ Eth0 is connected with lab node, where GTP interface gets created and PDU session is
established and traffic flows via this interface (Eth0 to Lab Network).

Figure 30: High level block diagram for the emulated setup for a NAT setup

➢ Below diagram is with DHCP server and it is with NAT disabled.

➢ Here when a user wants to communicate with any entity which is out of his/her domine or
Network, there will be a router which sits before the main router.
➢ Based on the destination IP address, the NAT reads it and translates the source to the particular
destination network IP address where the two source and destination are reachable.

Go to TOC Version: 1.8_5G SA Page 33 of 41

Magma Access Gateway

Figure 31: High level block diagram for the emulated setup for a DHCP setup

6.1.2 TEST ACTIVITY ON SPIRENT

➢ Have Access Gateway installed with V1.7 or upgrade it from the older version to V1.8 (Refer
Section 4.2 for AGW Upgrade)
➢ Verify whether all the 5G ports and the magma services are running successfully.
➢ Below are the commands used to verify all magma services and SCTP ports status are active or
not.
• Magma services: sudo service magma@* status
• 5G Port:
o sudo netstat -a | grep sctp
o cat /proc/net/sctp/eps
➢ When the test case runs, all required procedures (Registration, PDU-Establishment, Traffic, PDU-
Cleanup or Release and De-Registration) are triggered.
➢ Once the De-Registration is done i.e., cleanup is done, then the test case is stopped and all the
logs and PCAPs (Packet Captures) are collected and stored in the scenarios page, where user can
download it and analyze.

Go to TOC Version: 1.8_5G SA Page 34 of 41

Magma Access Gateway

Figure 32: Test Activity on Spirent

6.2 PERFORMANCE

➢ Performance Testing is done on Spirent test setup to verify and confirm the stability of AGW
with increasing load and for longer duration.
SOFTWARE BUILD INFO - 1.8.0-1663094999-49ED2E69
Scaling and Performance testing
Test Case Test Scenario Status
WLC_Scale_Test_1 200UE_5Rate_Registartion _DeRegistration Pass
WLC_Scale_Test_2 200UE_5Rate_1mbps_1Pdu_Registration and Pass
DeRegistration
WLC_Scale_Test_3 200UE_5Rate_2Mbps_Registration_DeRegistr Pass
ation
WLC_Scale_Test_4 200UE_5Rate_5Mbps_Registration_DeRegistr Pass
ation
WLC_Scale_Test_5 200UE_5Rate_50Mbps_Registration_DeRegis Pass
tration
WLC_Scale_Test_6 600UE_5Rate_Registration_DeRegistration Pass
WLC_Scale_Test_7 600UE_5Rate_1Mbps_1Pdu_Registration_De Pass
Registration
WLC_Scale_Test_8 600UE_5Rate_2Mbps_Registration_DeRegistr Pass
ation
Table 12: Performance

Go to TOC Version: 1.8_5G SA Page 35 of 41

Magma Access Gateway

SOFTWARE BUILD INFO - 1.8.0-1663094999-49ed2e69

Long Run testing
Testcase Testcase Name Test Description Dur Result
ID atio
n
TC001 TC001_Perormance_data_20 200UE register at 5UE/sec, push 2Mbps UDP 24hr Pass
0UE_2Mbps_UDP traffic for 10 mins then deregister. Continue s
the cycle for 15 loops
TC002 TC001_Perormance_data_20 200UE register at 5UE/sec, push 750Kbps/UE 1hr Pass
0UE_2Mbps_TCP TCP traffic for 1hr then deregister. Continue
the cycle for 15 loops
TC003 TC001_Performance_data_4 200UE Register at 5UE/sec, push 2Mbps per 1hrs Pass
00UE_1Mbps_UDP UE of traffic then deregister at 5UE/sec.
Trigger traffic for 8hrs per UE.

TC004 TC002_Performance_data_2 200UE Register at 5UE/sec, push 400Mbps of 8hrs Pass

00UE_400M_UDP traffic then deregister at 5UE/sec. Trigger
traffic for 8hrs per UE.

Table 13: Performance with Description & Duration

Note: Click here to find the test results and the debug logs of the above test cases.
➢ Testing is done through Spirent tool. Below is the screen shot of traffic graph from Spirent.

Figure 33: Spirent GUI 400Mbps traffic Graph

Go to TOC Version: 1.8_5G SA Page 36 of 41

Magma Access Gateway

7. TEST REPORT FROM CI PIPELINE

➢ Wavelabs CI/CD pipeline trigger happens on every build generated from CI-Master.
➢ Below are the steps involved in Pipeline trigger.
Step.1 Check for checkout from repo.
Step.2 Deploy and upgrade AGW.
Step.3 Trigger TC from Abot framework.
Step.4 Get test results information and download it.
Step.5 Sync of Abot test reports into test agent.

7.1 L IST OF A BOT TC RUNNING IN CI

➢ The purpose of running the test case in CI pipeline is to show that the test cases are Pass. It also
shows whether all the systems are working correctly or not and no issues found.
➢ WL CI/CD pipeline is designed to trigger test on every single build that occurs in gitrepo.
➢ Below is the link for CI/CD dash board.
Magma CI (magma-ci.web.app).
➢ Here is the CI/CD test summary report.

Test Execution Summary

Total # of TC 109
Pass (Count) 109
Pass (%) 100.00%
Fail (Count) 0
Fail (%) 0.00%
Table 14: CI/CD Test summary report

8. REAL EQUIPMENT TESTING-SIT

➢ Test activity is done on real device UE-SIT (Huawei, iPhone) and T&W gNB and magma 5G
SA AGW.

Note: Mobile device should be 5G enabled

8.1 T EST A CTIVITY ON R EAL D EVICE (UE)

➢ Configure the T&W Gnb, Magma-AGW and UE.

➢ Have Access Gateway installed with V1.8 or upgrade it from the older version to V1.8 (Refer
section 4.2 for AGW Upgrade)

Go to TOC Version: 1.8_5G SA Page 37 of 41

Magma Access Gateway

➢ Switch-on the mobile (Huawei mate UE) and turn-on Wi-Fi or Mobile data.
➢ Check for the 5G symbol in the network selection.
➢ Check whether the NGAP setup is established between the devices and all the 5G calls are
triggered from the device.
➢ To validate all the above steps, enable the PCAPs from AGW.

Figure 34: Test Activity on Real Device

➢ In below screen shot user could find the UE in Aeroplan mode, where the mobile data is turned-
off.

Figure 35: UE in Aeroplan mode

➢ Once the mobile data is turned-on in UE, 5G signal is detected and it registers with the network
(AGW) and the PDU session is successfully established.

Go to TOC Version: 1.8_5G SA Page 38 of 41

Magma Access Gateway

Figure 36: UE with 5G Signal Detected

➢ Once the PDU session is established, UE sends the traffic over the session.

Figure 37: Traffic sent by UE after PDU Establishment

8.2 L IST OF T EST C ASE

➢ Below are the list of test cases that are executed on the real mobile device.
Software Build info 1.8.0-1662060734-
83622a9e
Real Equipment Testing
Test Case Test Scenario Result
ID

Go to TOC Version: 1.8_5G SA Page 39 of 41

Magma Access Gateway

TC1 NGSetup Pass

TC2 Initial Registration - SUCI Based Pass

TC3 PDU Session Establishment Procedure (IPv4) Pass

TC4 Initial Registration and PDU session establishment - GUTI Based Pass

TC5 UE Triggered Service Request Pass

Table 15: Real Equipment Testing

Note:
➢ Click here to find the test results and the debug logs of the above test cases in T&W lab.

9. REFERENCES

• 3GPP TS 33.501 version 15.4.0 Release 15||Requirements on the UDM: Section # 5.8
• 3GPP TS 33.501 version 15.4.0 Release 15||Subscription identifier privacy: Section # 6.12
• 3GPP TS 33.501 version 15.4.0 Release 15||Subscription identifier de-concealing function
(SIDF): Section # 6.12.5
• 3GPP TS 33.501 version 15.4.0 Release 15||Elliptic Curve Integrated Encryption Scheme
(ECIES): Section # C.3
• 3GPP TS 24.501 version 15.6.0 Release 15||5GS mobility management messages: Section # 8.2
• 3GPP TS 24.501 version 15.6.0 Release 15||5GS session management messages: Section # 8.3
• 3GPP TS 24.501 version 15.6.0 Release 15||Timers of 5GS mobility management: Section # 10.2
• 3GPP TS 24.501 version 15.6.0 Release 15||Timers of 5GS session management: Section # 10.3
• 3GPP TS 29.281 version 15.7.0 Release 15||Echo Request: Section # 7.2.1
• 3GPP TS 29.281 version 15.7.0 Release 15||Echo Response: Section # 7.2.2
• 3GPP TS 29.281 version 15.7.0 Release 15||End Marker: Section # 7.3.2
• 3GPP TS 38.413 version 16.2.0 Release 16||PDU Session Management Messages: Section # 9.2.1
• 3GPP TS 38.413 version 16.2.0 Release 16||UE Context Management Messages: Section # 9.2.2
• 3GPP TS 38.413 version 16.2.0 Release 16||Paging Messages: Section # 9.2.4
• 3GPP TS 38.413 version 16.2.0 Release 16||NAS Transport Messages: Section # 9.2.5
• 3GPP TS 38.413 version 16.2.0 Release 16||Interface Management Messages: Section # 9.2.6
• TS 124 501 - V15.3.0 - 5G; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3
(3GPP TS 24.501 version 15.3.0 Release 15) (etsi.org)
• MM-Cause.xlsx (sharepoint.com)
• AGW installation Guide

Go to TOC Version: 1.8_5G SA Page 40 of 41