Public Network Access⚓︎
Enterprise access through the mobile operator's public radio network and the IPX beyond the basic 4G and 5G case of EXP-POL-002: 5G non-standalone (EN-DC) service on the 4G core path, 3G access through the operator's SGSN over Gp with MAP authentication and location management, and a device that changes between 4G and 3G on the public network.
| ID | Test | Category | Applies to |
|---|---|---|---|
| EXP-PUB-001 | 5G non-standalone (EN-DC) access through the public radio network | Functional | 4G, 5G · Public radio · Single node, HA cluster, Geo-redundant |
| EXP-PUB-002 | 3G access through the public radio network (Gp) | Functional | 3G · Public radio · Single node, HA cluster, Geo-redundant |
| EXP-PUB-003 | Change between 4G and 3G on the public radio network | Functional | 3G, 4G · Public radio · Single node, HA cluster, Geo-redundant |
EXP-PUB-001 — 5G non-standalone (EN-DC) access through the public radio network⚓︎
| Attribute | Value |
|---|---|
| Status | Accepted |
| Category | Functional |
| Components | xRouter, xCore, 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 5G-capable Mobile Asset on the mobile operator's network uses NR as a secondary radio (EN-DC) while its session stays on the 4G core path through Expeto Gateway (xRouter): the subscriber database permits NR as a secondary RAT, the operator's MME adds the NR leg, the UE shows 5G service, and traffic carried over NR reaches the enterprise LAN and is counted in the session record like any other traffic.
Preconditions
- Platform
- The operator's network offers EN-DC (NR non-standalone) at the test location and its MME supports the NR-as-secondary-RAT feature on S6a.
- An xCore in the public configuration and an xRouter are installed and integrated (EXP-POL-002 passed).
- Mobile Asset
- The Mobile Asset is Active with a System Profile whose APN the UE uses for data.
- Device
- A UE that supports EN-DC, with 5G (NSA) enabled in its settings and a network-type indicator.
- 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.
- 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 the xRouter (capture point 4) covering S6a and S8.
- Procedures executed first
Procedure
| # | Where | Action | Expected result |
|---|---|---|---|
| 1 | UE | Enable 5G (NSA) in the UE settings and connect through the operator's network with the enterprise APN. | The UE shows 5G service (the mobile operator's non-standalone indicator) while attached. |
| 2 | Capture | Inspect the S6a exchange at xRouter. | The Update Location Request from the operator's MME advertises the NR-as-secondary-RAT feature, and the Update Location Answer grants it and carries subscription data whose Access-Restriction-Data does not set "NR as Secondary RAT in E-UTRAN Not Allowed". |
| 3 | UE | Access a resource on the enterprise LAN and run the throughput measurement while the UE shows 5G. | The resource is reachable and the measurement completes. |
| 4 | xControl | Open the Mobile Asset. | The status is Connected and the network type is 4G. The session belongs to the 4G core, NR is a secondary radio, and the reported RAT type is E-UTRAN. |
| 5 | UE | Disable 5G on the UE (LTE only) and access the enterprise resource again; then re-enable 5G. | The UE shows 4G, then 5G again; the resource stays reachable and the UE keeps its address. |
| 6 | xControl | Disable mobile data on the UE, then open the closed session record. | The record's byte counts cover the traffic transferred while NR was active, and its radio access technology is E-UTRAN. |
Expected signalling
Capture points: S6a and S8 at xRouter (point 4), secure link (point 5).
4G (EPS) sequence
- Update Location Request from the operator's MME with Supported-Features (Feature-List-ID 2) indicating NR as Secondary RAT
- Update Location Answer with Supported-Features granting NR as Secondary RAT, and Subscription-Data whose Access-Restriction-Data does not forbid NR as a secondary RAT in E-UTRAN
- Create Session Request from the operator's SGW on S8 with RAT Type E-UTRAN; Create Session Response with the UE address
- Modify Bearer Request, Change Notification Request or Delete Session Request from the operator's SGW may carry Secondary RAT Usage Data Report IEs; the GTP proxy accepts them without effect on the session
- GTP-U on the secure link carrying the traffic transferred over both radios
Pass criteria
- The Update Location Answer grants NR as a secondary RAT and the UE obtains 5G (NSA) service with the enterprise APN.
- Traffic reaches the enterprise LAN while the UE is on NR, and the closed record counts it; the record's radio access technology is E-UTRAN.
- Disabling and re-enabling 5G on the UE leaves the session and the UE address in place.
Evidence collected: UE connectivity check; 3GPP signalling capture (pcap); xControl Mobile Asset status; Speed test result.
References: 3GPP TS 29.272 §7.3.10 (Supported-Features and Feature-List (NR as Secondary RAT)); 3GPP TS 29.272 §7.3.31 (Access-Restriction-Data); 3GPP TS 37.340 §4.1 (Multi-RAT Dual Connectivity overview (EN-DC)); 3GPP TS 29.274 §8.132 (Secondary RAT Usage Data Report).
EXP-PUB-002 — 3G access through the public radio network (Gp)⚓︎
| Attribute | Value |
|---|---|
| Status | Accepted |
| Category | Functional |
| Components | xRouter, xCore, xControl |
| Applies to | 3G · 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 Mobile Asset on a 3G (UMTS) cell of the mobile operator's network is authenticated by the HLR function of Expeto Gateway (xRouter) over MAP, registered from the operator's SGSN (and, on a combined attach, from its VLR), and given a PDP context terminated at the GTP proxy in xRouter over Gp with GTPv1, so that it reaches the enterprise LAN exactly as it does on 4G.
Preconditions
- Platform
- The operator's network has 3G (UTRAN) coverage at the test location, and its SGSN reaches the GTP proxy in xRouter over Gp through the IPX.
- The MAP signalling of xRouter toward the operator's signalling transfer point (SIGTRAN, M3UA) is configured and up; no
M3UAConnectionDownalert is active. - The HLR in xRouter allows UTRAN access for the Mobile Asset (the RAT types are allowed by default).
- Mobile Asset
- The Mobile Asset is Active with a System Profile whose APN the UE uses for data.
- Device
- A UE whose network mode can be locked to 3G ("3G only" or "WCDMA only").
- The UE has the APN of its System Profile configured.
- The UE has a web browser or a terminal application that can send ICMP echo requests (ping).
- Tooling and access
- Log in to xControl with an account that can view the Mobile Asset under test.
- A signalling capture at xRouter on the MAP side (capture point 11) and the Gp side (capture point 10).
- Procedures executed first
Procedure
| # | Where | Action | Expected result |
|---|---|---|---|
| 1 | UE | Set the network mode to 3G only and connect to the mobile operator's network with the enterprise APN. | The UE shows a 3G (UMTS or HSPA) connection. |
| 2 | Capture | Inspect the MAP capture. | SendAuthenticationInfo from the operator's SGSN is answered with UMTS authentication vectors; UpdateGprsLocation from the SGSN is answered after InsertSubscriberData carried the subscription with the APN; on a combined attach, UpdateLocation from the operator's VLR is answered as well. |
| 3 | Capture | Inspect the Gp capture. | Create PDP Context Request from the SGSN carries the enterprise APN and the IMSI; the Create PDP Context Response carries cause Request accepted and the UE's address; GTPv1-U follows. |
| 4 | UE | Access a resource on the enterprise LAN and transfer data in both directions. | The resource is reachable and traffic flows in both directions. |
| 5 | xControl | Open the Mobile Asset. | The status is Connected with network type 3G, and the session is attributed to the xRouter site. |
| 6 | UE | Disable mobile data on the UE. | The PDP context is deleted; xControl shows Disconnected and the closed record carries radio access technology UTRAN and the byte counts. |
Expected signalling
Capture points: MAP at xRouter (point 11), Gp at xRouter (point 10), secure link (point 5).
3G (UMTS, GPRS core) sequence
- SendAuthenticationInfo from the operator's SGSN to the HLR in xRouter, answered with UMTS authentication vectors
- UpdateGprsLocation from the SGSN; InsertSubscriberData from the HLR carrying the GPRS subscription with the APN; UpdateGprsLocation result
- On a combined GPRS and IMSI attach, UpdateLocation from the operator's VLR, InsertSubscriberData and its result
- Create PDP Context Request from the SGSN over Gp with the APN, the IMSI, the MSISDN and the requested QoS; Create PDP Context Response with cause Request accepted, the end-user address and the GTP-U tunnel endpoints
- GTPv1-U between the SGSN and the GTP proxy in xRouter, then GTP-U on the secure link to the xCore
- Delete PDP Context Request / Response when the UE disables data or detaches
Pass criteria
- The UE is authenticated over MAP and registered by the SGSN in the HLR, and the PDP context is accepted at the first attempt with an address from the Mobile Asset's System.
- The UE reaches the enterprise LAN in both directions over 3G.
- xControl shows the session as Connected with network type 3G, and the closed record carries radio access technology UTRAN and byte counts equal to the traffic sent.
Postconditions
- Set the UE's network mode back to automatic.
Evidence collected: 3GPP signalling capture (pcap); UE connectivity check; xControl Mobile Asset status; xControl session event log.
References: 3GPP TS 23.060 §6.5 (Attach function (GPRS attach); 3GPP TS 23.060 §9.2.2.1 (PDP Context Activation Procedure); 3GPP TS 24.008 §4.7.3 (GPRS attach procedure); 3GPP TS 29.002 §8.1 (Location management services (UpdateLocation); 3GPP TS 29.002 §8.5 (Authentication management services (SendAuthenticationInfo)); 3GPP TS 29.002 §8.8 (Subscriber management services (InsertSubscriberData)); 3GPP TS 29.060 §7.3.1 (Create PDP Context Request); 3GPP TS 29.060 §7.3.2 (Create PDP Context Response); 3GPP TS 29.060 §7.3.5 (Delete PDP Context Request).
EXP-PUB-003 — Change between 4G and 3G on the public radio network⚓︎
| Attribute | Value |
|---|---|
| Status | Accepted |
| Category | Functional |
| Components | xRouter, xCore, xControl |
| Applies to | 3G, 4G · Public radio · Single node, HA cluster, Geo-redundant |
| Duration | About 45 min |
| Prerequisite procedures | EXP-POL-002 — Enterprise access through the public radio network EXP-PUB-002 — 3G access through the public radio network (Gp) |
Objective. A dual-mode Mobile Asset that leaves 4G coverage for 3G on the mobile operator's network, and returns, keeps enterprise access with no user action: each serving node registers the UE with the subscriber database in xRouter over its own protocol (S6a from the MME, MAP from the SGSN), the PDN connection is either handed to the new node or re-established at the GTP proxy in xRouter, and the records show each radio access technology used. The 4G attach of a phone is a combined EPS and IMSI attach, so the operator's VLR registers with the HLR as well.
Preconditions
- Platform
- The operator's network offers both 4G and 3G coverage at the test location, and you can force the change (a place where 4G coverage ends, or the UE's network mode setting).
- EXP-PUB-002 passed, so the Gp and MAP integration is in place.
- Mobile Asset
- The Mobile Asset is Active with a System Profile whose APN the UE uses for data.
- Device
- A dual-mode 4G and 3G UE in automatic network mode (LTE preferred).
- The UE has the APN of its System Profile configured.
- The UE has a web browser or a terminal application that can send ICMP echo requests (ping).
- Tooling and access
- Log in to xControl with an account that can view the Mobile Asset under test.
- Signalling captures at xRouter on S6a and S8 (capture point 4), Gp (capture point 10) and MAP (capture point 11).
- Procedures executed first
Procedure
| # | Where | Action | Expected result |
|---|---|---|---|
| 1 | UE | Connect on 4G through the operator's network with the enterprise APN and start a continuous ping to a host on the enterprise LAN. | The UE shows 4G and replies arrive, as in EXP-POL-002. |
| 2 | Capture | Inspect the S6a and MAP captures for the attach. | Update Location Request / Answer on S6a from the operator's MME; where the UE performed a combined EPS and IMSI attach, an UpdateLocation from the operator's VLR arrives over MAP and is answered. |
| 3 | UE | Move to 3G-only coverage, or set the network mode to 3G only. Note the time. | The UE shows 3G within a minute and the ping recovers within 60 seconds of the change, either without interruption or after a short gap. |
| 4 | Capture | Inspect the MAP and Gp captures. | UpdateGprsLocation from the SGSN over MAP, and over Gp either an Update PDP Context Request for the existing context (the connection was handed over) or a Create PDP Context Request for a new one (re-established). Record which. |
| 5 | xControl | Open the Mobile Asset. | The status is Connected with network type 3G, and the Event Log shows the change. |
| 6 | UE | Return to 4G (automatic mode, or move back into 4G coverage). Note the time. | The UE shows 4G within a minute and the ping recovers within 60 seconds. |
| 7 | Capture | Inspect the S6a and S8 captures. | Update Location Request / Answer on S6a from the MME, and on S8 either a Modify Bearer Request for the existing connection or a Create Session Request for a new one. Record which. |
| 8 | xControl API | Stop the ping, disable mobile data, and list the Mobile Asset's session records for the period. | The records cover the whole period with no gap longer than 60 seconds; each record's radio access technology matches the access used (E-UTRAN, UTRAN), and the byte totals sum to the traffic sent. |
Expected signalling
Capture points: S6a and S8 at xRouter (point 4), Gp at xRouter (point 10), MAP at xRouter (point 11).
3G (UMTS, GPRS core) sequence
- UpdateGprsLocation from the operator's SGSN, InsertSubscriberData and the result, when the UE arrives on 3G
- Update PDP Context Request / Response over Gp for a handed-over connection, or Create PDP Context Request / Response for a re-established one
4G (EPS) sequence
- Update Location Request / Answer on S6a from the operator's MME, and UpdateLocation over MAP from the operator's VLR on a combined attach
- Modify Bearer Request / Response on S8 for a handed-over connection, or Create Session Request / Response for a re-established one, when the UE returns to 4G
Pass criteria
- Enterprise connectivity returns within 60 seconds of each change with no user action, and the UE keeps its address whenever the operator's network hands the connection over rather than re-establishing it.
- Each serving node's registration is answered by the subscriber database in xRouter (Update Location Answer on S6a, UpdateGprsLocation result over MAP), and a combined attach also produces an answered UpdateLocation from the VLR.
- The records for the period have no gap longer than 60 seconds, the radio access technology of each matches the access used, and the totals equal the traffic sent.
Postconditions
- Set the UE's network mode back to automatic.
Deployment notes
- Continuity mechanism: Whether the operator's network hands the PDN connection to the new serving node (Update PDP Context or Modify Bearer at the GTP proxy) or re-establishes it depends on the operator's core configuration; record the mechanism observed with the result.
Evidence collected: 3GPP signalling capture (pcap); UE connectivity check; xControl Mobile Asset status; xControl session event log.
References: 3GPP TS 23.401 §D.3 (Interoperation with Gn/Gp SGSNs); 3GPP TS 24.301 §5.5.1.3 (Combined attach procedure for EPS services and non-EPS services); 3GPP TS 29.060 §7.3.3 (Update PDP Context Request); 3GPP TS 29.274 §7.2.7 (Modify Bearer Request).