Data Service
This page covers the data-plane behavior changes on the 1NCE Platform 2.0: throughput enforcement, usage rounding, device-to-device traffic, multiple PDP sessions, and session timeouts.
QoS / throughput enforcement
| 1NCE Platform 1.0 | 1NCE Platform 2.0 | |
|---|---|---|
| Default limit | 1 Mbps | 1 Mbps |
| Enforcement | Only where roaming partners enforced it — customers could exceed the limit on non-enforcing networks | Strictly enforced for all networks |
On the 1NCE Platform 2.0, QoS limits are enforced per PDP context. The default is 1 Mbps, with custom speeds available. Packets exceeding the limit are dropped by the network, which can lead to retransmission attempts and transmission issues. Be aware of these limits when designing your application, especially for latency-sensitive or bulk-transfer workloads. If you need higher speeds, contact support.
Session rounding
| 1NCE Platform 1.0 | 1NCE Platform 2.0 | |
|---|---|---|
| Rounding | no rounding | Per PDP session, at session end (nearest KB) |
In v2 usage is rounded per PDP session at the end to the nearest kilobyte.
| Metric | 1NCE Platform 1.0 | 1NCE Platform 2.0 |
|---|---|---|
| 100 bytes in 1 PDP session | 0.1 KB | 1 KB (rounded up) |
| 100 × 1-byte PDP sessions | 0.1 KB | 100 KB (1 KB per session) |
| 1 PDP session with 100 × 1-byte sends | 0.1 KB | 1 KB (rounded up) |
Recommendation: Use long-running PDP sessions to minimize rounding impact. A single PDP session with multiple sends accrues less quota than many short sessions, since rounding applies only at session end.
Device-to-device (P2P) connectivity
Direct device-to-device (peer-to-peer) communication worked on the 1NCE Platform 1.0 and is not supported on the 1NCE Platform 2.0.
If you have devices that talk directly to each other over the cellular network, identify those flows and re-architect them to route through a backend service or internet breakout.
Multiple PDP sessions
Multiple PDP sessions are supported on the 1NCE Platform 2.0. However, for IoT devices, it is recommended to use only one active PDP session to avoid compatibility issues.
PDP context and GTP timeouts
GTP timeouts differ on the 1NCE Platform 2.0:
- GTP-C: there is no timeout on the 1NCE Platform 2.0, unlike the legacy 50-day reset behavior.
- GTP-U: a 7-day timeout closes the PDP session. This timeout is reset by any single data byte sent or received.
What to do
- If you need throughput higher than 1 Mbps, contact support for custom speed options.
- Use long-running PDP sessions to minimize quota consumption from rounding.
- Identify and re-architect any device-to-device traffic to use backend services or internet breakout.
- For IoT devices, use only one active PDP session.