Skip to content

Testing and Validation Procedures

UE Initiated Attach⚓︎

Description

A UE (subscriber) initiates an attach request to the network where it is authenticated.
After the authentication is passed, the network obtains the UE's subscription data from the subscriber database.
Based on the default APN and PDN/PDU context in the subscription data, the network creates default session; and then the UE is attached to the network.

Prerequisite

  • Log into xControl with an appropriate user role
  • UE (Mobile Asset/Subscriber) is provisioned to an appropriate Expeto ‘System’ in xControl with the status 'Provisioned'
  • UE is powered off or in airplane mode
  • UE has the APN configured
  • UE has a web browser application or terminal application with ICMP
  • Start signal tracing (pcap) using preferred tool to capture 3GPP signalling traffic
Action Expected Result
  1. Power on the UE or come out of the Airplane mode
  2. Wait for it to connect to the cellular network
  3. Initiate traffic by navigating to an internet page or ping a known available resource
  1. Verify the UE has a cellular data connection
  2. Verify internet traffic or ping is working on the UE
  3. In xControl, verify the UE (Mobile Asset) is in Connected status and has an IP address
  4. In xControl, verify the UE's Session Event log has appropriate entries
  5. Verify signalling traces match the expected 3GPP flow.

UE initiated Detach⚓︎

Description

UE initiates a detach procedure and release the session.

Prerequisite

  • Log into xControl as Admin role
  • Start signal tracing (pcap) using a preferred tool to capture 3GPP signalling traffic
Action Expected Result
Execute Test: UE Initiated Attach
  1. Power off the UE or put it in the Airplane mode
  2. Wait for the UE to disconnect from the network
  1. In xControl, verify the UE (Mobile Asset) is in Disconnected status within reasonable time (nominally within 30 seconds)
  2. In xControl, verify the UE's Session Event log has appropriate entries
  3. Verify signalling traces match the expected 3GPP flow.

Network-initiated Detach⚓︎

Description The network (core) initiates a detach procedure and releases the session.

Prerequisite

  • Log into xControl as Admin role
  • Start signal tracing (pcap) using prefered tool to capture 3GPP signalling traffic
Action Expected Result
Execute Test: UE Initiated Attach
  1. In xControl, invoke the "Cancel Session" action for the subscriber (Mobile Asset)
  2. Wait for the UE to disconnect from the network
  1. In xControl, verify the UE is in Disconnected status
  2. In xControl, verify the Session Event log has appropriate entries
  3. Verify signalling traces match the expected 3GPP flow.
    NOTE: the UE may try to reconnect after the disconnect

UE Idle Mode⚓︎

Description Validate UE can go into inactivity (ECM-IDLE) mode

Prerequisite

  • UE has a web browser application or terminal application with ICMP
  • Start signal tracing (pcap) using a preferred tool to capture 3GPP signalling traffic
Action Expected Result
Execute Test: UE Initiated Attach
  1. Ensure UE is not generating data traffic.
  2. Wait the required time as defined by the radio configuration.
    Note: The wait time is dependent on the radio's idle-mode timer. If this is unknown, use an Android or similar app.
  1. For private radios, use CLI to verify the MME session is marked as Idle
  2. Alternatively, use the app on UE to verify it is Idle (inactive)
  3. Verify signalling traces match the expected 3GPP flow.

UE Service Request⚓︎

Description

When a UE is registered at a network, but its connection was released due to inactivity (ECM-IDLE), new traffic is generated from the UE, changing the network connection state to connected.

Prerequisite

  • UE has a web browser application or terminal application with ICMP
  • Start signal tracing (pcap) using a prefered tool to capture 3GPP signalling traffic
  • Log into xControl as Admin role
Action Expected Result
Execute Test: UE Initiated Attach
Execute Test: UE Idle Mode
  1. Initiate traffic by navigating to an internet page or ping a known available resource
  1. Verify the UE has a cellular data connection
  2. Verify internet traffic or ping is working on the UE
  3. In xControl, verify the UE (Mobile Asset) is in Connected status
  4. Verify signalling traces match the expected 3GPP flow.

UE Paging⚓︎

Description

The network side initiates a service request procedure to establish a connection with UE in idle mode.

Prerequisite

  • Tool to generate ping (or similar other traffic) from the network towards the UE's IP address, which could be on actual PGW/UPF or another environment close to it
  • Start signal tracing (pcap) using a preferred tool to capture 3GPP signalling traffic
  • Log into xControl as Admin role
Action Expected Result
Execute Test: UE Initiated Attach
Execute Test: UE Idle Mode

Use the preferred tool (ping) to initiate traffic from a network toward the IP address of the UE.
  1. Verify that the ping returns the expected result - If UE does not respond to the ping, try another protocol/tool to initiate network data
  2. Verify signalling traces match the expected 3GPP flow.

Multiple UE Attach⚓︎

Description

Test connecting multiple UEs to the network.

Prerequisite

  • The same preconditions as "UE Initiated Attach" test cases, except multiple UEs are provisioned in xControl.
Action Expected Result
Execute Test: UE Initiated Attach

Repeat the Action from Step 1 for each of the provisioned Subscribers (UEs)

Repeat the Expected Result from Step 1 for each of the provisioned Subscribers (UEs)

Unknown UE Attach⚓︎

Description

When a UE not provisioned in xControl initiates an attach request to the network, the network rejects the attach attempt.

Prerequisite

  • Log into xControl as with an appropriate user role
  • UE (Mobile Asset/Subscriber) is NOT provisioned in xControl
  • UE is powered off or in airplane mode
  • Start signal tracing (pcap) using prefered tool to capture 3GPP signalling traffic"
Action Expected Result
  1. Power on the UE or come out of the Airplane mode
  2. Wait for the UE to attempt to connect to the cellular network
  1. Verify the UE fails to connect the the network
  2. Verify signalling traces match the expected 3GPP flow.

Inactive Subscriber attach⚓︎

Description An inactive subscriber in the xControl, initiates an attach request to the network and the network rejects the attach attempt

Prerequisite

  • Log into xControl with an appropriate user role xControl but marked as inactive/disabled
  • UE is powered off or in airplane mode
  • Start signal tracing (pcap) using a preferred tool to capture 3GPP signalling traffic
Action Expected Result
Execute Test: Deactivate Subscriber
  1. Power on the UE or come out of the Airplane mode
  2. Wait for the UE to attempt to connect to the cellular network
  1. Verify the UE fails to connect the the network
  2. Verify signalling traces match the expected 3GPP flow.

Expeto Edge (xCore) Session Management High Availability K8s⚓︎

Description

Expeto Edge, managed by Kubernetes, continues to operate even when the node(s) hosting the session management services fails.

Prerequisite

  • An xCore is deployed on Kubernetes (K8s) and operational
  • Identify the node (VM) where the pods responsible for session management (SMF/PGW-C) are running
  • Ensure there are sufficient nodes available to host the session management
  • Ensure a subscriber (device) is connected and passing data
Action Expected Result
  1. Shutdown the node hosting the session management pod(s) (SMF/PGW-C)
  2. Put the device in airplane mode
  3. Then turn off the airplane mode
  4. Perform speedtest
  1. Verify that all pods on the node start successfully on the other nodes.
  2. Verify the subscriber can authenticate and connect to the network.
  3. Run a speedtest and verify the device can upload and download data.

Deactivate Subscriber⚓︎

Description An active subscriber is deactivated in the xControl, UE initiates an attach request to the network and the network rejects the attach attempt.

Prerequisite

  • Log into xControl with an appropriate user role
  • Start signal tracing (pcap) using a preferred tool to capture 3GPP signalling traffic
Action Expected Result
Execute Test: UE Initiated Attach
  1. Change the status of the subscriber (mobile asset) to 'inactive' in xControl
  2. Wait for the subscriber's status to change to Disconnected.
  1. Verify the UE disconnected from the network and any reconnection attempts fail
  2. Verify signalling traces match the expected 3GPP flow.

Reactivate Subscriber⚓︎

Description

An active subscriber is deactivated in the xControl, UE initiates an attach request to the network, and the network rejects the attach attempt.

Prerequisite

  • UE is powered on and not in airplane mode
  • UE has APN correctly configured
  • UE has a web browser application or terminal application with ICMP
  • Start signal tracing (pcap) using a prefered tool to capture 3GPP signalling traffic
  • Log into xControl as Admin role
Action Expected Result
Execute Test: Deactivate Subscriber
  1. Change the status of the subscriber (mobile asset) to 'active' in xControl
  2. Wait for the device to reconnect and re-establish the connection
  3. Wait for the subscriber's status to change to Connected.
  1. Verify the UE has a cellular data connection
  2. Verify internet traffic or ping is working on the UE
  3. In xControl, verify the UE (Mobile Asset) is in Connected status
  4. Verify signalling traces match the expected 3GPP flow.

Limit Bandwidth (AMBR)⚓︎

Description

When the subscriber UL/DL AMBR is reduced in the xControl with a new profile, the UL/DL rate of the UE is reduced.

Prerequisite

  • Log into xControl with an appropriate user role
  • UE has a web browser application
  • A tool that can measure upload and download speeds.
  • Start signal tracing (pcap) using a preferred tool to capture 3GPP signalling traffic
Action Expected Result
Execute Test: UE Initiated Attach
  1. Run a speedtest to get initial bandwidth numbers
  2. Create a new or use existing profile in xControl with significantly reduced UL/DL AMBR
  3. In xControl, edit the subscriber, change the profile to the new profile and save.
  4. Wait for the UE to detach and attach back the network
  5. Run the speed test on the UE browser and note down the upload and download speeds.
  1. In xControl, verify the UE's Session Event log has appropriate entries as the UE is detached and attaches back to the network.
  2. Verify that the upload and download speeds on the UE are lower after the new profile is applied to the subscriber.
  3. Verify signalling traces match the expected 3GPP flow.

Expeto Edge (xCore) restart recovery⚓︎

Description

Non-redundant Expeto Edge (xCore) recovers after all resource(s) hosting the xCore are power cycled (turned off and back on)

Prerequisite

  • An xCore is deployed and operational
  • Ensure a subscriber (device) is connected and passing data
Action Expected Result
  1. Shutdown all node(s)/VM(s) hosting the xCore site
  2. Start all the node(s)/VM(s) that were shutdown 
  1. Verify all the services of the xCore is running
  2. Verify the subscriber reconnects to the network
  3. Run a speedtest and verify the device can upload and download data.

Expeto Gateway (xRouter) restart recovery⚓︎

Description

Non-redundant Expeto Gateway (xRouter) recovers after all resource(s) hosting the xRouter are power cycled (turned off and back on)

Prerequisite

  • An xRouter is deployed and operational
  • The xRouter is integrated with an xCore
  • Ensure a subscriber (device) is connected the xCore through the xRouter and passing data
Action Expected Result
  1. Shutdown all node(s)/VM(s) hosting the xRouter site
  2. Start all the node(s)/VM(s) that were shutdown 
  1. Verify all the services of the xRouter is running
  2. Verify the subscriber reconnects to the network through the xRouter
  3. Run a speedtest and verify the device can upload and download data.

Expeto xControl restart recovery⚓︎

Description

Non-redundant Exepto xControl recovers after all resource(s) hosting xControl are power cycled.

Prerequisite

  • An Control is deployed and operational
  • An xCore site is deployed and managed by the xControl
  • You have an account in xControl
Action Expected Result
  1. Log into the xControl and confirm the status of the xCore site
  2. Shutdown all node(s)/VM(s) hosting the xControl
  3. Start all the node(s)/VM(s) that were shut down 
  1. Verify that xControl starts without any errors
  2. You able to log back into the xControl
  3. Verify the status of the xCore status

Expeto Gateway (xRouter) Subscriber Management high availability K8s⚓︎

Description

Expeto Gateway, managed by Kubernetes, continues to operate when the node(s) hosting the subscriber management services fail. 

Prerequisite

  • An xRouter is deployed on Kuberntes (K8s) and operational
  • Identify the node (VM) where the pods responsible for subscriber mangement (for 5G - AUSF, UDR and UDM and  for 4G - HSS) are running
  • Ensure there are sufficient nodes available to host the subscriber mangement after node shutdown
  • Ensure a subscriber (device) is connected and passing data
Action Expected Result
  1. Shutdown the subscriber node(s)
  2. Put the device in airplane mode
  3. Then turn off the airplane mode 
  4. Steps 2 and 3 might need to be repeated until authentication or update location operations occur due to how some visited networks may cache authentication data fetched prior to node shutdown
  1. Verify all pods on node start successfully on the other nodes
  2. Verify the subscriber can authenticate and connect to the network.

Expeto Edge (xCore) Geographical Redundancy⚓︎

Description

When an xCore deployed in a geo-redundant configuration fails, subscribers from the xCore reconnect to the redundant xCore and continue to get service.

 

Prerequisite

  • Geo-redundant xCores deployed in active-active configuration
  • Subscribers (devices) connected to both xCores and passing traffic
Action Expected Result
  1. Run a speedtest on a device connected to one of the xCore sites
  2. Record the speed and the latency 
  3. Shutdown the xCore site
  1. The device connected to the xCore that was shutdown should disconnect from the xCore
  2. The device should then reconnect to the redundant xCore site within a reasonable time
  3. Run a speedtest on the device
  4. Verify the speed and the latency are acceptable

Expeto Edge (xCore) Datapath High Availability K8s⚓︎

Description

Expeto Edge, managed by Kubernetes, continues to operate even when the node(s) hosting the datapath services fails.

Prerequisite

  • An xCore is deployed on Kubernetes (K8s), and operational
  • Identify the node (VMs) where the pods responsible for datapath (UPF/PGW-U) is running
  • Ensure there are sufficient nodes available to host the datapath
  • Ensure a subscriber (device) is connected and passing data
Action Expected Result
  1. Shutdown the datapath node (UPF/PGW-U)
  2. Put the device in airplane mode
  3. Then turn off the airplane mode
  4. Perform speedtest
  1. Verify all pods on node start successfully on the other nodes
  2. Verify the subscriber can authenticate and connect to the network.
  3. Run speedtest and verify the device can upload and download data.

Expeto Gateway (xRouter) Geographical Redundancy⚓︎

Description

When an xRouter deployed in a geo-redundant configuration fails, subscribers connected through the xRouter will reconnect through the redundant xRouter and continue to get service.

Prerequisite

  • Geographically redundant xRouters are deployed and operational
  • Both the xRouters integrated with an xCore
  • Subscribers (devices) connected through both xRouters to the xCore and passing traffic
Action Expected Result
  1. Run speedtest on a device connected through one of the xRouter sites
  2. Record the speed and the latency 
  3. Shutdown the xRouter site
  1. The device connected through the xRouter that was shutdown should disconnect from the xRouter
  2. The device should then reconnect to the xCore site through the other geo-redundant xRouter
  3. Run speedtest on the device
  4. Verify the speed and the latency are acceptable

Prevent UE to UE communication⚓︎

Description

The network rejects communication between UEs (subscribers) provided on the Expeto platform.

Prerequisite

  • An xCore is deployed and operational
  • The xCore is configured to prevent UE to UE communication (default configuration)
  • The xCore has a System 
  • Two UEs are provisioned into the System
Action Expected Result
Execute Test: Multiple UE Attach
  1. Log into xControl
  2. Find the target UE
  3. Note down the target UE's IP address
  4. From the source UE, ping the target UE's IP address
  1. Verify ping fails to reach the target UE

Prevent UE communication with internal xCore components⚓︎

Description

The network rejects any communication from the UE to any software components of the Expeto platform.

Prerequisite

  • An xCore is deployed and operational
  • The xCore is configured to prevent UE to UE communication (default configuration)
  • The xCore has a system where the UE are provisioned
Action Expected Result
Execute Test: UE Initiated Attach
  1. Log into xControl
  2. Find the UE (Mobile Asset) on the Mobile Assets page
  3. Navigate to the Site details page of UE and node down the IP addresses of the Site and monitoring endpoints.
  4. From the source UE, ping the IP addresses
  1. Verify ping fails to reach the target IP addresses

Expeto Edge (xCore) maximum subscribers (UEs)⚓︎

Description

Non-redundant Expeto Edge (xCore) shall support the maximum number of active subscribers as designed.

Prerequisite

  • An xCore is deployed and operational
  • The xCore has a System 
Action Expected Result
Execute Test: UE Initiated Attach
  1. Repeat the previous step until the number of active subscribers (UEs) connected reaches the maximum the xCore can support.
  1. Verify all the UEs are connected
  2. Verify the UEs are able to pass traffic