Event Data: Platform 1.0 → 2.0
An event record captures a notable system occurrence related to a SIM or device (device connect/disconnect, PDP context create/delete, quota reached, SIM status changes, location updates).
Summary of changes
The 1NCE Platform 1.0 event stream and Data Streamer 2.0 share the same structure and identical data types for all shared fields. The main differences are:
- Location fields renamed — flat location fields are split into GTP version-specific fields.
- New operational fields added — VPN, failure diagnostics, auto-topup, session correlation.
- 1NCE Platform 1.0 portal/user fields retired — user-activity tracking fields are not carried over.
What stays the same
The following fields are identical in name, type, and meaning:
| Group | Fields |
|---|---|
| Identifiers | id, timestamp, ingestion_timestamp |
| Event classification | alert, description, event_severity_id, event_source_id, event_type_id |
| Device / SIM | endpoint_* fields, sim_id, imsi_id |
| Organization | organisation_id |
| Client info | detail_client_* fields |
| Network detail | detail_country_id, detail_id, detail_mnc, detail_tapcode, most detail_pdp_context_* fields |
| Volumes | detail_volume_rx, detail_volume_tx, detail_volume_total |
Fields that are renamed
| 1NCE Platform 1.0 field | Data Streamer 2.0 field |
|---|---|
detail_session_id | detail_pdp_context_ipcan_session_id |
detail_pdp_context_ci | detail_pdp_context_gtp_v1_uli_ci |
detail_pdp_context_lac | detail_pdp_context_gtp_v1_uli_lac |
detail_pdp_context_rac | detail_pdp_context_gtp_v1_uli_rac |
detail_pdp_context_sac | detail_pdp_context_gtp_v1_uli_sac |
On the 1NCE Platform 1.0, fields like ci and lac were flat but had different meanings depending on the GTP version. Data Streamer 2.0 separates them to avoid ambiguity.
Fields that are new
New operational fields
| New field | What it contains |
|---|---|
detail_auto_topup_effective | Whether auto top-up was applied (true/false) |
detail_data_service_failure_cause | Reason for a data service failure |
detail_reason | General event reason description |
vpn_id | VPN connection identifier |
vpn_provision_status_id | VPN provisioning status |
New geolocation fields (GTP v2 — 4G/5G)
Entirely new for 4G/5G, providing precise cell identification that was not available before:
| New field | What it contains |
|---|---|
detail_pdp_context_gtp_v2_uli_cgi_ci | Cell Identity (CGI) |
detail_pdp_context_gtp_v2_uli_cgi_lac | Location Area Code (CGI) |
detail_pdp_context_gtp_v2_uli_eci | E-UTRAN Cell Identifier |
detail_pdp_context_gtp_v2_uli_emenbi | Extended Macro eNodeB ID |
detail_pdp_context_gtp_v2_uli_lac | Location Area Code |
detail_pdp_context_gtp_v2_uli_menbi | Macro eNodeB ID |
detail_pdp_context_gtp_v2_uli_rai_lac | Location Area Code (RAI) |
detail_pdp_context_gtp_v2_uli_rai_rac | Routing Area Code (RAI) |
detail_pdp_context_gtp_v2_uli_sai_lac | Location Area Code (SAI) |
detail_pdp_context_gtp_v2_uli_sai_sac | Service Area Code (SAI) |
detail_pdp_context_gtp_v2_uli_tac | Tracking Area Code |
Fields that are retired
These relate to 1NCE Platform 1.0 portal user activity and are not relevant to network/device events in Data Streamer 2.0:
| Retired field | What it contains |
|---|---|
user_id, user_name, user_username | 1NCE Platform 1.0 portal user identity |
detail_stale | 1NCE Platform 1.0 data-freshness indicator |
detail_support_user_org_id, detail_support_username | 1NCE Platform 1.0 support-access tracking |
detail_target_username | Target user of an action (1NCE Platform 1.0 user management) |
detail_trusted_device_id, ..._browser, ..._operating_system, ..._activation_date | 1NCE Platform 1.0 MFA / trusted-device feature |
detail_pdp_context_tariff_profile_id | Platform 1.0-specific tariff profile concept |
Practical impact
- Update location queries: replace
detail_pdp_context_ci/lac/rac/sacwith the GTP version-specific equivalents —gtp_v1_uli_*for 2G/3G,gtp_v2_uli_*for 4G/5G. - Session correlation field renamed: update
detail_session_id→detail_pdp_context_ipcan_session_id. - Portal/user-activity events are not carried over (logins, MFA, support access). They are Platform 1.0-specific.
- New diagnostics:
detail_data_service_failure_causeanddetail_reason. - VPN tracking: events carry explicit
vpn_id. - Richer 4G/5G location: new
gtp_v2_uli_eciandgtp_v2_uli_tacprovide precise cell identification. - Resolve IDs to names via the Reference Data (v2 API) endpoints; cache responses locally.