QoS is a multi-provider network intelligence engine that continuously measures the performance of each device or fleet across networks, operators, and coverage areas. It provides real insights such as: 

• Which operator offers the best real-world performance 
• Network degradation detection 
• Regional roaming quality 
• Latency, throughput, and jitter scores 
• Attach / registration failures 
• API-driven quality metrics for IoT orchestration 
• SLA verification 
• Pre-switching intelligence for Multi-IMSI & SGP.32 orchestration 

QoS is valuable for: 

• IoT service providers 
• Mobile operators 
• eSIM travel providers 
• Enterprise fleets 
• Device OEMs 

QoS answers critical questions such as: 

• Is the device experiencing poor connectivity due to the operator or the device itself? 
• Which operator delivers the best latency in region X? 
• Should the fleet switch from IMSI A to IMSI B? 
• Is a connectivity partner failing its SLA? 

QoS transforms raw connectivity data into actionable intelligence. 

QoS collects performance metrics from: 

• Device signaling events 
• Network registration logs 
• IP connectivity checks 
• OTA network probes 
• DNS resolution tests 
• HTTP/HTTPS latency tests 
• Optional deep client-side telemetry (if OEM-integrated) 

These metrics come from: 

• Smartphones 
• IoT devices 
• Routers / CPE 
• POS terminals 
• Wearables 
• Any device using Valid connectivity 

The engine processes: 

• Signal quality 
• Throughput 
• Round-trip time 
• Packet loss 
• Attach failures 
• Radio access technology (2G/3G/4G/5G/LTE-M/NB-IoT) 
• Roaming indicators 
• Location data (optional) 
• IMSI movement between networks 

It identifies: 

• Network outages 
• Coverage issues 
• SIM provisioning problems 
• Roaming inconsistencies 
• Operator degradation 
• Opportunity for profile switching 

QoS converts raw metrics into simplified KPIs: 

• Availability Score 
• Quality Score 
• Network Responsiveness 
• Stability Score 
• Attach Success Rate 
• Coverage Index 

Scores can be seen per: 

• Region 
• Farm/Fleet 
• Device 
• Operator 
• IMSI 

This layer enables: 

• Alerts 
• Automated switching logic 
• API-triggered actions 
• Reporting dashboards 

It informs: 

• eIM (SGP.32 IoT Manager) 
• Multi-IMSI switching engines 
• SM-Connect orchestration 

Operators can view: 

• Global coverage on heatmaps 
• Operator performance rankings 
• Device-specific QoS summary 
• IMSI-level analytics 
• Alerts & anomalies 
• KPI trends 

The QoS Engine collects more than 50 network metrics. 
Below is the standardized set. 

• Download speed 
• Upload speed 
• Latency (RTT) 
• Jitter 
• Packet loss 
• DNS resolution time 
• Time-to-first-byte 

• RSSI 
• RSRP 
• RSRQ 
• SINR 
• TAC (LTE/5G) and LAC (2G/3G) changes 
• RAT changes (2G–5G, LTE-M/NB-IoT) 
• Cell attach time 

Location insights are derived from radio parameters such as MCC/MNC, TAC, LAC, Cell ID, and other network indicators. QoS does not rely on GPS or device-side geolocation; instead, it uses network-level signaling information to infer service conditions. 

• APN success rate 
• Attach success rate 
• PDP activation rate 
• IP session uptime 
• Network handover stability 

Per operator: 

• Attach failures 
• Reject causes (3GPP codes) 
• Roaming attach issues 
• RAN congestion patterns 

• Sleep/wake behavior 
• Battery impact 
• Firmware-driven reconnection cycles 
• IPAd/IPAe orchestration performance 

QoS ranks networks by: 

• Performance 
• Availability 
• Stability 

This is essential for: 

• eSIM travel providers 
• IoT service providers 
• Enterprises choosing operators 

QoS verifies whether connectivity partners meet promised SLAs: 

• Latency 
• Availability 
• Roaming coverage 

Alerts are triggered when violations occur. 

QoS feeds metrics into the multi-IMSI applet logic: 

• Best operator selection 
• Automatic fallback 
• Pre-emptive switching 
• Regional optimizations 

QoS prioritizes: 

• When to trigger profile switching 
• Whether fallback is needed 
• Which operator performs better in region X 
• When to re-enable bootstrap 

QoS differentiates between: 

• Network issue 
• Device issue 
• Firmware problem 
• SIM provisioning error 

Supports: 

• Operator support teams 
• Enterprise front-line helpdesks 

QoS identifies: 

• Poor roaming partners 
• Cross-border connectivity issues 
• Regions requiring manual IMSI steering 

Shows: 

• Global coverage heatmap 
• Performance tier by operator 
• Device distribution 
• Alerts 
• Regional KPIs 

Shows for each device: 

• Active operator 
• IMSI used 
• RAT & signal metrics 
• Latency/throughput 
• Last connectivity event 
• Historical performance chart 

Ranking per region: 

• Operator A 
• Operator B 
• Operator C 

Based on: 

• Latency 
• Stability 
• Attach rate 
• Jitter 

Useful for multi-operator strategies. 

Alerts triggered by: 

• Network degradation 
• High failure rates 
• Regional outages 
• SLA violations 
• Device anomaly events 

Available reports: 

• Daily fleet quality 
• Regional performance 
• Operator trend report 
• Device stability ranking 
• IMSI-level analytics 

Exports: 

• CSV 
• PDF 
• API push 

APIs available to: 

• IoT platforms 
• Operator support systems 
• Multi-IMSI engines 
• SGP.32 eIM orchestrator 
• CRM systems 

Returns: 

• Signal 
• Throughput 
• Latency 
• Operator ID 
• Location (optional) 

Returns: 

• Degradation events 
• Regional anomalies 
• Network changes 

Used for: 

• Real-time steering decisions 
• Multi-IMSI switching logic 
• Fleet management policies 

Retrieve: 

• Entire fleet KPIs 
• Operator comparative scores 
• Regional datasets 

This section shows how QoS integrates with Valid’s other connectivity technologies. 

If QoS detects: 

• Poor performance 
• High latency 
• Frequent attach failures 
• Local operator outage 

Then it triggers: 

• Switch IMSI 
• Fall back to preferred operator 
• Re-attach 

QoS feeds SGP.32 orchestration to support: 

• Profile switching 
• Region-based provisioning 
• Recovery flows 
• Operator replacement 

For eSIM apps like Airalo, QoS: 

• Monitors partner operators 
• Recommends best network per country 
• Ensures user experience consistency 

Possible causes: 

• Device offline 
• No IP session 
• Firmware update pending 

Resolution: 

• Validate connectivity 
• Retry connectivity test 

Possible causes: 

• Congested RAN 
• Roaming partner degradation 
• Incorrect APN 

Resolution: 

• Switch IMSI 
• Update operator policy 

Causes: 

• Network instability 
• Outdoor → indoor movement 
• IoT power saving mode 

Resolution: 

• Trigger fallback 
• Validate RAT selection 

Causes: 

• RAN congestion 
• Throttling 
• Misconfigured data plan 

Resolution: 

• Trigger operator change 
• Validate subscription settings 

QoS follows: 

• Data minimization principles 
• GDPR compliance 
• ISO-aligned processes 
• Secure data transport 
• Role-based access 

It does not collect: 

• Personal content 
• Application usage 
• Location unless explicitly enabled

1. Always Validate KPIs Before Switching IMSI

Avoid unnecessary profile switches. 

2. Segment IoT Policies by Device Type

Example: 

• Telematics = mobility-focused 
• Smart meters = power-efficient 
• POS = low-latency 

3. Use Alerts for Early Warning

Automate operator change when degradation is detected. 

4. Combine QoS with SM-Connect

This ensures: 

• Complete troubleshooting 

• Unified connectivity overview 

• Intelligent automation