Skip to content

Policy and Traffic⚓︎

Policy configured in xControl is enforced on the user plane and applied to live sessions without a re-attach: bandwidth limits and quality of service from the System Profile, egress through the System's subnet, roaming restrictions from Roaming Profiles and Carrier Groups, per-network APN overrides for Mobile Assets on the mobile operator's public radio network, network slice selection on 5G, and correct handling of large packets.

ID Test Category Applies to
EXP-POL-001 Limit bandwidth (AMBR) Functional 4G, 5G · Local radio, Public radio · Single node, HA cluster, Geo-redundant
EXP-POL-002 Enterprise access through the public radio network Functional 4G, 5G · Public radio · Single node, HA cluster, Geo-redundant
EXP-POL-003 System egress mapping Functional 4G, 5G · Local radio, Public radio · Single node, HA cluster, Geo-redundant
EXP-POL-004 Quality of service profile applied to the session Functional 4G, 5G · Local radio, Public radio · Single node, HA cluster, Geo-redundant
EXP-POL-005 Per-network APN override on the public radio network Functional 4G, 5G · Public radio · Single node, HA cluster, Geo-redundant
EXP-POL-006 Roaming Profile restriction on the public radio network Security 4G, 5G · Public radio · Single node, HA cluster, Geo-redundant
EXP-POL-007 Large packets and MTU Functional 4G, 5G · Local radio, Public radio · Single node, HA cluster, Geo-redundant
EXP-POL-008 Network slice selection (5G) Functional 5G · Local radio · Single node, HA cluster, Geo-redundant

EXP-POL-001 — Limit bandwidth (AMBR)⚓︎

Attribute Value
Status Accepted
Category Functional
Components xCore, xControl
Applies to 4G, 5G · Local radio, Public radio · Single node, HA cluster, Geo-redundant
Duration About 30 min
Prerequisite procedures EXP-SES-001 — UE-initiated attach
Included in Installation and Upgrade Verification

Objective. When the Mobile Asset is moved to a System Profile with lower uplink and downlink bitrates (AMBR) in xControl, the subscriber database pushes the change into the live session: the bearer is modified without a detach, the UE keeps its address, and the measured upload and download throughput drops to the new limits.

Preconditions

  • Device
    • The UE has a web browser application.
  • Tooling and access
    • Log in to xControl with an account that holds the ADMIN role.
    • A tool that measures upload and download throughput from the UE against a server on the enterprise network, such as iperf3 or OpenSpeedTest.
    • Start a 3GPP signalling capture (pcap) with your preferred tool on the interfaces the procedure exercises.
  • Procedures executed first

Procedure

# Where Action Expected result
1 — Execute EXP-SES-001 — UE-initiated attach as a prerequisite procedure. As defined in EXP-SES-001.
2 UE Run a speed test and record the upload and download results as the baseline. Baseline upload and download figures are recorded.
3 xControl Create, or select, a System Profile whose APN Profile has a significantly lower Upload Bitrate and Download Bitrate than the current one (for example one quarter). The System Profile is available on the Mobile Asset's System.
4 xControl On the Mobile Asset's detail page click Edit, select the new System Profile, and click Submit. The change is saved.
5 xControl Open the Mobile Asset and its Event Log. The status stays Connected with the same IP address; the session record stays Open; no detach and no new session.
6 Capture Inspect the signalling capture. The messages match the sequence under Expected signalling; the modified bearer or session carries the new bitrate limits, and there is no Detach Request or Deregistration Request.
7 UE Run the speed test again and record the upload and download results. Both figures are below the baseline and do not exceed the new limits.

Expected signalling

Capture points: S6a / N8 (point 4), S11 / N4 (point 3), S1-MME / N2 (point 1).

4G (EPS) sequence

  1. Insert Subscriber Data Request on S6a from the HSS with the new APN-AMBR, and Insert Subscriber Data Answer
  2. Modify Bearer Command on S11 from the MME, then Update Bearer Request from the PGW and Update Bearer Response
  3. E-RAB Modify Request / Response and Modify EPS Bearer Context Request / Accept carrying the new APN-AMBR

5G (5GS) sequence

  1. Nudm_SDM_Notification from the UDM with the new subscribed Session-AMBR
  2. PFCP Session Modification Request / Response on N4
  3. PDU Session Resource Modify Request / Response carrying PDU Session Modification Command with the new Session-AMBR, and PDU Session Modification Complete

Pass criteria

  • The change takes effect with no detach and no new session; the UE keeps its address.
  • The signalled AMBR values equal the bitrates configured in the APN Profile.
  • Measured upload and download after the change do not exceed the new limits.

Postconditions

  • Restore the original System Profile if later tests assume it.

Evidence collected: Speed test result; xControl session event log; 3GPP signalling capture (pcap).
References: 3GPP TS 23.401 §4.7.3 (Bearer level QoS parameters (APN-AMBR)); 3GPP TS 23.401 §5.3.9.2 (Insert Subscriber Data procedure); 3GPP TS 23.401 §5.4.2.1 (HSS Initiated Subscribed QoS Modification); 3GPP TS 23.501 §5.7.2.6 (Session-AMBR); 3GPP TS 23.502 §4.3.3.2 (UE or network requested PDU Session Modification).


EXP-POL-002 — Enterprise access through the public radio network⚓︎

Attribute Value
Status Accepted
Category Functional
Components xRouter, xCore
Applies to 4G, 5G · Public radio · Single node, HA cluster, Geo-redundant
Duration About 20 min
Included in Installation and Upgrade Verification

Objective. A Mobile Asset attached through the mobile operator's public radio network is authenticated by Expeto Gateway (xRouter), reaches the enterprise private LAN through the customer-dedicated xCore, and passes upload and download traffic.

Preconditions

  • Platform
    • An xCore in the public configuration is installed and operational.
    • An xRouter is installed, configured, and integrated with that xCore.
  • Mobile Asset
    • The Mobile Asset is imported into xControl and authorized (state Active).
  • Tooling and access
    • Log in to xControl with an account that can view the Mobile Asset under test.
    • A signalling capture at the xRouter (capture point 4) and on the secure link (capture point 5).

Procedure

# Where Action Expected result
1 UE Connect the UE to the mobile operator's public network. The UE shows a connection to the public network.
2 UE Access a resource on the enterprise private LAN. The resource is reachable from the UE.
3 UE Transfer data in both directions (for example, upload and download a file). Upload and download traffic is sent and received.
4 xControl Open the Mobile Asset. The status is Connected and the session is attributed to the xRouter site.
5 Capture Inspect the captures. The authentication and session setup arrive at xRouter from the operator's core, and only GTP-U user-plane traffic crosses the secure link.

Expected signalling

Capture points: S6a / N8 at xRouter (point 4), secure link (point 5).

4G (EPS) sequence

  1. Authentication Information Request / Answer and Update Location Request / Answer from the operator's MME to the HSS in xRouter
  2. Create Session Request / Response from the operator's SGW to the GTP proxy in xRouter (S8)
  3. GTP-U on the secure link between xRouter and the xCore

5G (5GS) sequence

  1. Authentication and subscription exchanges from the operator's core to the UDM in xRouter
  2. N9 session setup toward the GTP proxy in xRouter
  3. GTP-U on the secure link between xRouter and the xCore

Pass criteria

  • The UE reaches the enterprise LAN and passes traffic in both directions.
  • No signalling crosses the secure link; only user-plane traffic does.

Evidence collected: UE connectivity check; xControl Mobile Asset status; 3GPP signalling capture (pcap).


EXP-POL-003 — System egress mapping⚓︎

Attribute Value
Status Accepted
Category Functional
Components xCore, xControl
Applies to 4G, 5G · Local radio, Public radio · Single node, HA cluster, Geo-redundant
Duration About 30 min
Prerequisite procedures EXP-SES-001 — UE-initiated attach
EXP-SES-007 — Multiple UE attach

Objective. Each System's Mobile Assets receive addresses from that System's range and their traffic leaves the xCore on that System's egress network, so that the enterprise can segment its network by System.

Preconditions

  • Platform
    • The Site has two Systems, A and B, with different address ranges and different egress networks (for example two VLANs), each with a host that answers ping.
  • Mobile Asset
    • One Mobile Asset on System A and one on System B, both connected (EXP-SES-007).
  • Tooling and access
    • Log in to xControl with an account that can view the Mobile Asset under test.
    • A capture on each egress network (capture point SGi / N6).
  • Procedures executed first

Procedure

# Where Action Expected result
1 — Execute EXP-SES-007 — Multiple UE attach as a prerequisite procedure. As defined in EXP-SES-007.
2 xControl Open each Mobile Asset and note its IP address. Each address is inside its own System's range.
3 UE From UE A, ping the host on System A's egress network; from UE B, ping the host on System B's. Both pings are answered.
4 Capture Inspect the egress captures during the pings. UE A's packets appear only on System A's egress network and UE B's only on System B's, each with the UE's address as source (or the System's translated address where source address translation is configured).
5 UE From UE A, ping the host on System B's egress network. The ping is answered only if the enterprise network routes between the two egress networks; record the result.

Pass criteria

  • Every Mobile Asset's address is inside its System's range.
  • Every Mobile Asset's traffic leaves on its own System's egress network and on no other.

Deployment notes

  • Source address translation: Where a System's address pool is configured for source address translation on egress, the packets on the egress network carry the translated address; otherwise they carry the UE's address unchanged.

Evidence collected: xControl screenshot; ICMP result from the UE; 3GPP signalling capture (pcap).


EXP-POL-004 — Quality of service profile applied to the session⚓︎

Attribute Value
Status Accepted
Category Functional
Components xCore, xControl
Applies to 4G, 5G · Local radio, Public radio · Single node, HA cluster, Geo-redundant
Duration About 25 min
Prerequisite procedures EXP-SES-001 — UE-initiated attach

Objective. The quality-of-service class configured in the Mobile Asset's APN Profile is signalled to the radio and the UE at session setup, and a change of profile is pushed into the live session by the subscriber database without a detach.

Preconditions

  • Platform
    • Two System Profiles exist on the System whose APN Profiles differ in QoS (for example QCI 9 and QCI 6).
  • Tooling and access
    • Log in to xControl with an account that holds the ADMIN role.
    • Start a 3GPP signalling capture (pcap) with your preferred tool on the interfaces the procedure exercises.
  • Procedures executed first

Procedure

# Where Action Expected result
1 — Execute EXP-SES-001 — UE-initiated attach as a prerequisite procedure. As defined in EXP-SES-001.
2 Capture Inspect the session setup in the capture. The QoS class and priority match the APN Profile of the Mobile Asset's current System Profile.
3 xControl On the Mobile Asset's detail page click Edit, select the other System Profile, and click Submit. The change is saved.
4 Capture Inspect the signalling capture. The messages match the sequence under Expected signalling; the modified bearer or QoS flow carries the new class and priority; there is no Detach Request or Deregistration Request.
5 xControl Open the Mobile Asset. The status stays Connected with the same IP address and the same open session.

Expected signalling

Capture points: S6a / N8 (point 4), S11 / N4 (point 3), S1-MME / N2 (point 1).

4G (EPS) sequence

  1. At setup, Create Session Response on S11 carrying the bearer QoS (QCI, ARP); Initial Context Setup Request carrying the E-RAB level QoS parameters and Activate Default EPS Bearer Context Request carrying the EPS QoS
  2. On the change, Insert Subscriber Data Request / Answer on S6a, Modify Bearer Command, Update Bearer Request / Response, E-RAB Modify Request / Response and Modify EPS Bearer Context Request / Accept carrying the new QCI and ARP

5G (5GS) sequence

  1. At setup, PDU Session Establishment Accept carrying the authorized QoS rules and QoS flow descriptions (5QI); PDU Session Resource Setup Request carrying the QoS flow level parameters
  2. On the change, Nudm_SDM_Notification, PFCP Session Modification Request / Response, PDU Session Resource Modify Request / Response carrying PDU Session Modification Command with the new 5QI and ARP, PDU Session Modification Complete

Pass criteria

  • The signalled QoS class and priority equal the configured values at setup and after the change.
  • The change is applied to the live session with no detach and the same address.

Postconditions

  • Restore the original System Profile if later tests assume it.

Evidence collected: 3GPP signalling capture (pcap); xControl session event log.
References: 3GPP TS 23.401 §4.7.3 (Bearer level QoS parameters); 3GPP TS 23.401 §5.4.2.1 (HSS Initiated Subscribed QoS Modification); 3GPP TS 23.501 §5.7.1 (QoS model); 3GPP TS 23.502 §4.3.3.2 (UE or network requested PDU Session Modification).


EXP-POL-005 — Per-network APN override on the public radio network⚓︎

Attribute Value
Status Accepted
Category Functional
Components xRouter, xControl
Applies to 4G, 5G · Public radio · Single node, HA cluster, Geo-redundant
Duration About 30 min
Prerequisite procedures EXP-POL-002 — Enterprise access through the public radio network

Objective. An APN override configured for a specific Carrier in the Mobile Asset's System Profile is applied when the UE is served by that network, taking precedence over the APN Profile's own bitrates.

Preconditions

  • Platform
    • The public network the UE uses exists as a Carrier in xControl.
  • Tooling and access
    • Log in to xControl with an account that holds the ADMIN role.
    • A tool that measures upload and download throughput from the UE against a server on the enterprise network, such as iperf3 or OpenSpeedTest.
    • A signalling capture at xRouter (capture point 4).
  • Procedures executed first

Procedure

# Where Action Expected result
1 — Execute EXP-POL-002 — Enterprise access through the public radio network as a prerequisite procedure. As defined in EXP-POL-002.
2 UE Run a speed test and record the baseline. Baseline figures are recorded.
3 xControl Open System Profiles, edit the Mobile Asset's System Profile, open the APN Profiles tab, click Add Carrier Override for the Carrier of the public network, set significantly lower bitrates, and click Submit. The override is saved.
4 Capture Inspect the capture at xRouter. The HSS pushes the change to the operator's MME with an Insert Subscriber Data Request carrying the override's APN-AMBR; the bearer is updated without a detach.
5 UE Run the speed test again. Upload and download are below the baseline and do not exceed the override.

Pass criteria

  • The override's bitrates are applied to the live session when the UE is on the named network, without a detach.

Postconditions

  • Remove the override.

Evidence collected: Speed test result; 3GPP signalling capture (pcap).


EXP-POL-006 — Roaming Profile restriction on the public radio network⚓︎

Attribute Value
Status Accepted
Category Security
Components xRouter, xControl
Applies to 4G, 5G · Public radio · Single node, HA cluster, Geo-redundant
Duration About 30 min
Prerequisite procedures EXP-POL-002 — Enterprise access through the public radio network

Objective. A Roaming Profile whose Allowed Carrier Groups exclude the public network the UE is on causes the attach to be refused, and adding the network's Carrier Group restores service.

Preconditions

  • Platform
    • The public network the UE uses exists as a Carrier in a Carrier Group in xControl.
    • A Roaming Profile exists whose Allowed Carrier Groups do not include that Carrier Group.
  • Tooling and access
    • Log in to xControl with an account that holds the ADMIN role.
    • A signalling capture at xRouter (capture point 4).
  • Procedures executed first

Procedure

# Where Action Expected result
1 — Execute EXP-POL-002 — Enterprise access through the public radio network as a prerequisite procedure. As defined in EXP-POL-002.
2 xControl On the Mobile Asset's detail page click Edit, select the restrictive Roaming Profile, and click Submit. The change is saved.
3 UE Toggle airplane mode so that the UE attaches again through the public network. The UE fails to obtain service.
4 Capture Inspect the capture at xRouter. The location update from the operator's core is answered with a roaming-not-allowed error, and the UE receives a reject.
5 xControl Edit the Roaming Profile, add the network's Carrier Group to Allowed Carrier Groups, and click Submit. The change is saved.
6 UE Toggle airplane mode again. The UE connects as in EXP-POL-002.

Expected signalling

Capture points: S6a / N8 at xRouter (point 4).

4G (EPS) sequence

  1. Update Location Request from the operator's MME answered with an error result for roaming not allowed
  2. Attach Reject to the UE from the operator's MME

5G (5GS) sequence

  1. The subscription retrieval from the operator's AMF is refused for the serving PLMN
  2. Registration Reject to the UE from the operator's AMF

Pass criteria

  • The UE obtains no service while its Roaming Profile excludes the serving network.
  • The Update Location Answer carries the roaming-not-allowed error and the UE receives EMM cause #11, PLMN not allowed (4G), or 5GMM cause #11 (5G), so it stops retrying this network and continues PLMN selection on others.
  • Service returns once the Carrier Group is allowed.

Postconditions

  • Restore the Mobile Asset's original Roaming Profile.

Evidence collected: 3GPP signalling capture (pcap); xControl session event log.
References: 3GPP TS 29.272 §5.2.1.1 (Update Location procedure (roaming not allowed)); 3GPP TS 24.301 §5.5.1.2.5 (Attach not accepted by the network).


EXP-POL-007 — Large packets and MTU⚓︎

Attribute Value
Status Accepted
Category Functional
Components xCore
Applies to 4G, 5G · Local radio, Public radio · Single node, HA cluster, Geo-redundant
Duration About 25 min
Prerequisite procedures EXP-SES-001 — UE-initiated attach

Objective. Packets up to the link MTU the network signals to the UE pass end to end without fragmentation, larger packets are handled per the configuration, and bulk TCP transfers do not stall.

Preconditions

  • Device
    • The UE has a terminal application that can send pings of a chosen size with the do-not-fragment flag set.
  • Tooling and access
    • Start a 3GPP signalling capture (pcap) with your preferred tool on the interfaces the procedure exercises.
    • A host on the enterprise LAN that answers ping and runs an iperf3 server.
  • Procedures executed first

Procedure

# Where Action Expected result
1 — Execute EXP-SES-001 — UE-initiated attach as a prerequisite procedure. As defined in EXP-SES-001.
2 Capture In the capture of the attach, read the IPv4 link MTU the network provides to the UE (protocol configuration options in the Attach Accept, or the PDU Session Establishment Accept). The signalled MTU is recorded; if none is signalled, record that.
3 UE Ping the LAN host with a payload that produces an IP packet of the signalled MTU (or 1400 bytes if none was signalled), with the do-not-fragment flag set. The ping is answered.
4 UE Ping the LAN host with an IP packet of 1500 bytes, do-not-fragment set. The ping is answered, or the UE reports that fragmentation is needed; record which.
5 Capture Inspect the user-plane capture on the egress network during the pings. Packets at the signalled MTU arrive unfragmented.
6 UE Run an iperf3 test toward the LAN host for 60 seconds in each direction. Throughput is stable and the transfer does not stall.

Pass criteria

  • The network signals a link MTU of at least 1400 bytes to the UE.
  • Packets at the signalled MTU pass unfragmented in both directions.
  • The 60-second TCP transfers complete without stall in either direction.

Evidence collected: 3GPP signalling capture (pcap); UE connectivity check; Speed test result.
References: 3GPP TS 24.301 §6.5.1.3 (UE requested PDN connectivity procedure accepted by the network (protocol configuration options)).


EXP-POL-008 — Network slice selection (5G)⚓︎

Attribute Value
Status Accepted
Category Functional
Components xCore, xControl
Applies to 5G · Local radio · Single node, HA cluster, Geo-redundant
Duration About 30 min

Objective. A 5G UE requests network slices at registration. The AMF grants exactly the slices the Mobile Asset is subscribed to, the PDU session is established on an allowed slice and carries its S-NSSAI to the radio and the user plane, and a request for a slice the Mobile Asset is not subscribed to is refused.

Preconditions

  • Platform
    • The Site's AMF advertises the S-NSSAIs supported for the Site's PLMN and tracking areas (in the access-mobility configuration of the core, plmnTacSliceList with supportedSnssais), and the user plane maps each S-NSSAI to the System's DNN.
    • You know the S-NSSAIs written into the Mobile Asset's subscription by xControl (its default single NSSAIs, for example SST 1 and SST 1 with SD 000001).
  • Mobile Asset
    • The UE's Mobile Asset is provisioned in xControl on the System under test, with state Active and status Provisioned or Disconnected.
  • Device
    • A 5G SA UE whose Requested NSSAI can be set (or a UE that requests the network's default slice) and, for the negative step, a UE or simulator that can request an S-NSSAI not in the subscription.
    • The UE has the APN of its System Profile configured.
  • Tooling and access
    • Log in to xControl with an account that can view the Mobile Asset under test.
    • Start a 3GPP signalling capture (pcap) with your preferred tool on the interfaces the procedure exercises.
    • Access to the CLI.

Procedure

# Where Action Expected result
1 UE Power on the UE, or take it out of airplane mode, and wait for it to register and establish its data session. The UE shows a data connection.
2 Capture Open the Registration Request. The Requested NSSAI lists the slice or slices the UE asked for.
3 Capture Open the Registration Accept. The Allowed NSSAI equals the S-NSSAIs of the Mobile Asset's subscription; a requested S-NSSAI outside the subscription appears in the Rejected NSSAI with cause "S-NSSAI not available in the current PLMN".
4 Capture Open the PDU Session Establishment Request and Accept, and the PDU Session Resource Setup Request on N2. The request carries an allowed S-NSSAI and the System's DNN; the Accept and the N2 message carry the same S-NSSAI; the PFCP session on N4 is established on the user plane serving that DNN.
5 CLI Run cd /nr, then read amf <imsi>. The context lists the allowed NSSAI and the PDU session with its S-NSSAI and DNN.
6 UE Pass traffic to a host on the enterprise network. The traffic is answered.
7 xControl Open the Mobile Asset. The status is Connected with an address from the System's range.
8 UE Request a PDU session on an S-NSSAI that is not in the Allowed NSSAI (with a UE that allows it, or the simulator). The request is refused; no session is created for it and the existing session is unaffected.
9 Capture Inspect the refusal. The network rejects the PDU Session Establishment Request for the non-allowed S-NSSAI, and no PFCP session is established for it.

Expected signalling

Capture points: N2 (point 1), N4 (point 3).

5G (5GS) sequence

  1. Registration Request with Requested NSSAI
  2. Registration Accept with Allowed NSSAI equal to the subscribed S-NSSAIs, and Rejected NSSAI for any non-subscribed S-NSSAI requested
  3. Registration Complete; UE Configuration Update Command with Configured NSSAI when the network sends one
  4. PDU Session Establishment Request with S-NSSAI and DNN
  5. PFCP Session Establishment Request / Response on N4 toward the user plane serving the DNN
  6. PDU Session Resource Setup Request carrying the S-NSSAI and PDU Session Establishment Accept with the S-NSSAI
  7. For a non-allowed S-NSSAI, the establishment is rejected and no N4 session is created

Pass criteria

  • The Allowed NSSAI in the Registration Accept equals the Mobile Asset's subscribed S-NSSAIs; every other requested S-NSSAI is rejected.
  • The PDU session carries an allowed S-NSSAI end to end (NAS, N2, AMF context) and passes traffic.
  • A PDU session on a non-allowed S-NSSAI is refused without affecting the established session.

Evidence collected: 3GPP signalling capture (pcap); CLI output; xControl Mobile Asset status.
References: 3GPP TS 23.501 §5.15.5.2.1 (Network slice selection at registration); 3GPP TS 23.502 §4.2.2.2.2 (General Registration (Allowed NSSAI)); 3GPP TS 24.501 §5.5.1.2.4 (Initial registration accepted by the network (Allowed and Rejected NSSAI)); 3GPP TS 24.501 §6.4.1.2 (UE-requested PDU session establishment procedure initiation (S-NSSAI); 3GPP TS 29.503 §5.2.2.2 (Subscription data retrieval (NSSAI)).