Data Streamer Migration
This set of pages describes the data field changes you will experience when upgrading from the 1NCE Platform 1.0 data streams to Data Streamer 2.0. Use it to assess the impact on your integrations before the upgrade.
Background
The 1NCE Platform 1.0 delivers connectivity event and usage data streams. Data Streamer 2.0 provides the same core connectivity data with platform-specific enhancements, and supports both your existing SIM cards on the 1NCE Platform 1.0 core network and new SIM cards on the 1NCE Platform 2.0 core network.
What changes for customers
| Aspect | Change |
|---|---|
| Data content | Core connectivity data (events, usage, volumes, SIM/device info) remains the same |
| Field naming | Some fields are renamed (for example, session_id → ipcan_session_id) |
| Field availability | Some Platform 1.0-specific fields are retired; new fields are added |
| Location data | Richer geolocation via GTP v1/v2 User Location Information (ULI) fields |
The 1NCE Platform 1.0 event stream is richer than the Data Streamer 2.0 equivalent in some areas. Validate your integrations against the field-level mapping pages below — do not assume a one-to-one mapping.
Integration and delivery changes
Beyond the schema, how the data reaches you also changes:
- Retired destinations: the AWS S3, Datadog, and KeenIO integrations are retired and are not available with Data Streamer 2.0. Move affected streams to Webhook (REST) or AWS Kinesis. Affected customers are informed before their upgrade.
- Source IPs change: the platform source IPs that deliver stream data to your backend change with the upgrade (your SIM IP addresses do not change). If your backend or firewall allowlists the Data Streamer source IPs, update the allowlist — the new IPs are communicated with your technical notification, or contact 1NCE Technical Support.
- SMS Forwarder: the SMS Forwarder is integrated into Data Streamer 2.0 and works the same way.
Migration guides
| Guide | Contents |
|---|---|
| Event Data: Platform 1.0 → 2.0 | Field changes for event records |
| Usage Data: Platform 1.0 → 2.0 | Field changes for usage records |
| Reference Data (v2 API) | API v2 endpoints for resolving IDs to names |
Each guide follows the same structure: what stays the same, what is renamed, what is new, and what is retired.
Key terminology
| Term | Meaning |
|---|---|
| Usage record | A record of data consumption (volume transmitted/received) or SMS activity for a SIM during a session |
| Event record | A record of a system occurrence (device connected, PDP context created/deleted, quota reached, etc.) |
| PDP Context | Packet Data Protocol context — the data connection allowing a device to transmit IP data over the mobile network |
| ICCID | Integrated Circuit Card Identifier — unique SIM card number |
| IMSI | International Mobile Subscriber Identity — unique subscriber number on the SIM |
| IMEI | International Mobile Equipment Identity — unique device hardware identifier |
| MNO | Mobile Network Operator |
| MCC / MNC | Mobile Country Code / Mobile Network Code — together they identify a specific operator in a country |
| RAT | Radio Access Technology (2G, 3G, 4G, 5G, NB-IoT, LTE-M) |
| GTP | GPRS Tunnelling Protocol — used for mobile data connections (v1 for 2G/3G, v2 for 4G/5G) |
| ULI | User Location Information — geolocation data within GTP signaling |
| IP-CAN | IP Connectivity Access Network — the session identifier in Data Streamer 2.0 |