Summary

  • A green application probe proves reachability, not that traffic used the contracted S-NSSAI, DNN, user-plane path or service treatment.
  • Accept a 5G slice only with a time-bound receipt that joins commercial entitlement to admission, session, path, measurement and explicit fallback evidence.

At 09:00, during a resilience exercise commissioned by an enterprise, the serving operator removes the intended slice entitlement from the test subscription. The monitored application never goes dark. The handset still registers, a data session still forms, and packets still reach the service. The operations dashboard records continuity.

That result looks reassuring until the team asks a different question: which service carried the packets after 09:00? If the device obtained usable connectivity through a default or alternative selection, the test may have demonstrated application resilience while saying nothing about the contracted slice. Isolation, priority, latency policy, jurisdictional routing or slice-specific monitoring could have vanished without changing the colour of the uptime tile.

The problem is not that fallback is inherently improper. A default or alternative service can be a legitimate part of mobile operation and a valuable continuity mechanism. The problem is evidentiary: a continuity test can silently change the object being tested. When the contract sells differentiated network treatment, generic reachability is not proof of delivery.

One service label, several network states

3GPP does not describe slice use as a single Boolean. TS 23.501 distinguishes Configured NSSAI, Default Configured NSSAI, Requested NSSAI, Allowed NSSAI, Partially Allowed NSSAI and rejected S-NSSAIs. These names mark different stages and decisions. What a subscription or device is configured to request is not necessarily what the serving network allows in the current access type and registration area.

The distinction matters at the moment of failure. An S-NSSAI can be rejected for a whole public land mobile network, for a registration area, for part of one, or because of congestion. A serving network can map slice identifiers in roaming, and the architecture includes an Alternative S-NSSAI mechanism. During slice removal, associated PDU sessions can be released and the device may need to register again to obtain a valid Allowed NSSAI.

None of those procedures proves that an ordinary application must fail closed. Nor do they establish that every operator product will behave the same way. They do show why a screenshot of a 5G indicator, a successful registration or a working application cannot independently attest to the commercial service being delivered.

TS 24.501 adds another boundary. The device requests, receives, stores and updates slicing information through NAS procedures, while the subset it presents can depend on implementation and upper-layer preferences. A commercial test therefore has to observe both sides of the selection exchange rather than treating a product name in an order form as a packet-path fact.

The SLA object extends beyond the radio

GSMA's Generic Network Slice Template turns a use case into a structured set of attributes. Those attributes can include availability, area of service, throughput, isolation, the permitted number of devices and PDU sessions, performance monitoring, reliability, and session or service continuity. GSMA also separates customer, provider, communication-service and network-operator roles, even when one company occupies several of them.

This is a useful corrective to radio-centric acceptance. A visible 5G state only says something about access. A slice can span terminal, access, core and transport domains, combining dedicated and shared resources. The traffic's DNN, selected user-plane function, transport treatment and measurement context may matter as much as the radio connection.

Shared infrastructure is part of the economic appeal. An operator can sell differentiated treatment without building a physically separate network for every customer. But the same resource sharing makes the acceptance evidence more valuable. If the enterprise cannot distinguish its contracted service from ordinary connectivity, the SLA risks becoming a promise about configuration rather than a verifiable delivery obligation.

Build a slice-specific acceptance receipt

The right acceptance object is not a dashboard screenshot. It is a signed or otherwise tamper-evident receipt for a defined test window, assembled from evidence held by the enterprise, device estate and operator. At minimum, it should bind:

  1. the subscription, device identity or test cohort, serving PLMN and access type;
  2. the configured and requested S-NSSAIs, the Allowed or Partially Allowed NSSAI, and any rejection, roaming mapping or alternative selection;
  3. the DNN and PDU-session identity, with timestamps for establishment, modification and release;
  4. the selected user-plane path and enough transport evidence to distinguish the intended treatment from ordinary service;
  5. the contracted service attributes and the measurements used to evaluate them; and
  6. an explicit fallback state: permitted, prohibited, degraded-but-billable, or continuity-only and excluded from the slice SLA.

The receipt should be tested at boundaries, not only during steady state. Change registration area. Introduce congestion. Remove and restore the entitlement in a controlled window. Exercise roaming where relevant. Confirm what happens to existing sessions and new sessions separately. A resilient application may preserve connections while a new session follows a different policy, or the reverse.

Commercial remedies should follow the same object. If fallback preserves business continuity but no longer supplies contracted isolation or priority, the contract can credit that interval without treating it as a total outage. If fallback is prohibited for a regulated workload, the device or application policy may need to fail closed. These are product and risk decisions; the network should make the resulting state observable.

The governing principle is simple: measure the service that was bought. Reachability can remain an important operational signal, but it should sit beside—not substitute for—proof of admission, session selection, user-plane placement and slice-specific performance. A 5G SLA is healthy only when the evidence stays bound to the same slice while the chart remains green.