MOBILE NETWORKS · REAL SERVICE VALIDATION
Validate mobile services where they actually need to work.
Continuously validate voice, data, roaming and mobile Internet services from distributed locations using real mobile modules, real networks and real SIM identities.
Go beyond network availability. Validate the service outcome.

SERVICE AVAILABILITY IS NOT SERVICE SUCCESS
A registered device does not mean the service actually works.
A mobile device can be attached to the network while voice, data, DNS, application access or roaming services still fail or degrade. Continuous validation checks the outcome from the service perspective.
Related insights
REAL MOBILE SERVICES
Validate the services subscribers actually use.
Voice
Validate real voice service availability and call behaviour using supported mobile modules and network environments.
Data & Internet
Validate mobile data connectivity, DNS, Internet reachability and defined services from distributed locations.
Roaming
Validate service availability and behaviour using real SIM identities across different visited networks and locations even within one test suite and minutes.
REAL SIM. DIFFERENT LOCATION.
Move the SIM identity — not the engineer.
TRADITIONAL
ACCTOPUS REMOTE SIM
A SIM can be validated from BER, FRA or LAX without physically shipping the SIM between test locations.
CONTROL THE VALIDATION
Choose the network, location, SIM and service you want to validate.
Persistent mobile Explorers allow operators to run defined validations under controlled conditions instead of waiting for suitable measurements to appear.
LEGACY TEST SYSTEMS
CONTROLLED DEGUST VALIDATION
Operators may opt for several SIM storage servers in different locations/countries to support inbound and outbound roaming validation without ever losing control over the SIM cards and profiles in their countries.
FROM 2G TO 5G
Use the mobile environment that matches the service you need to validate.
Related insights
ROAMING VALIDATION
Validate the same subscriber identity across different networks and locations.
Finding: controlled validation separates SIM identity from the physical test location.
Using real SIM identities with distributed Explorers makes it possible to compare service behaviour across visited networks and locations without changing the subscriber identity.
VALIDATE THE SERVICE — NOT JUST THE TRAFFIC VOLUME
Use real traffic where it matters. Simulate service consumption where it makes more sense.
Not every validation scenario requires consuming the full amount of real user traffic.
Related insights
REAL PRODUCT
Mobile validation using distributed or moving Explorers.
Degust combines service results, Explorer context, SIM information and supporting network evidence in an operational view.

FROM MOBILE SERVICE TO EVIDENCE
Validate, compare and investigate mobile service outcomes.
SELECT
Choose location, network environment, SIM identity and validation scenario.
VALIDATE
Run the defined voice, data, roaming or service validation.
COMPARE
Compare results across locations, networks, technologies or other relevant context.
INVESTIGATE
Use service results and supporting network evidence to focus further investigation.
MOBILE USE CASES
One validation platform. Different mobile questions.
Service Assurance
Continuously validate whether defined mobile voice, data and Internet services actually work from distributed locations.
Roaming
Compare service behaviour for real SIM identities across visited networks and locations.
Integration
Use Degust results, exports and selected operational views within existing network and service-assurance environments.
MOBILE OPERATOR QUESTIONS
Questions mobile operators need to answer.
How can a mobile operator verify that a service actually works, not just that the device is registered?
Registration confirms that a device has attached to the network, but it does not prove that voice, data, DNS, Internet or application services work as expected. Controlled service validation checks the actual outcome from distributed mobile locations. This often reveals issues with policies and tariffs of your subscribers abroad, often introduced by your roaming partners.
How can mobile voice and data services be validated continuously from distributed locations?
Persistent mobile Explorers can run scheduled or continuous voice, data and service validations using supported mobile modules and real SIM identities. Results can then be qualified and compared centrally.
How can an operator validate roaming without physically moving SIM cards between test locations?
Real SIM cards can be hosted in Acctopus SIM infrastructure (hosted in datacenters of your choice) and their required identity information made available to distributed test devices during validation sessions. This allows the same SIM identity to be used from different test locations within minutes without physically shipping the SIM. Imagine a travel experience from Berlin to Amsterdam to Miami in just minutes... day by day.
Why use real SIM identities for mobile service validation?
A real SIM identity preserves the subscriber and roaming context required for many mobile service scenarios. This makes it possible to validate how defined services behave for the actual subscription rather than relying only on simulated subscriber assumptions.
Why not use eSIM for mobile service validation?
While one could use eSIM for roaming scenarios, most operators don't want to spend the extra money for constantly reprovisioning the same eSIM profile to the necessary devices at the locations under test.
How can the same SIM identity be compared across different visited networks?
The same hosted SIM identity can be assigned to distributed Explorers in different locations and network environments. Validation results can then be compared while keeping the subscriber identity consistent.
Can Degust validate 5G NSA and 5G SA environments?
Degust uses 5G mobile modules and Explorer configurations for relevant NSA and SA validation scenarios.
What is the difference between mobile network monitoring and mobile service validation?
Network monitoring observes infrastructure, signalling and network health. Mobile service validation checks whether defined services such as voice, data or Internet access actually work from relevant distributed locations. Degust complements network monitoring with this service-outcome perspective.
How can a mobile operator run targeted validation during an incident?
Persistent Explorers allow validation to be targeted by location, technology, SIM identity or other available metadata. The same scenario can be repeated on affected and comparison locations under controlled conditions.
Can mobile service validation use real phones as well as dedicated mobile modules?
Yes, real phones can be used in selected scenarios. Most distributed Degust Explorers use Linux-based systems with dedicated mobile modules because they provide a controllable platform for continuous remote validation.
How can mobile roaming scenarios be validated without consuming large amounts of real data to save international operator charging?
Where the validation objective does not require transferring the full user data volume, selected signalling or service-consumption scenarios can be used instead. Degust can support appropriate Diameter or HTTPS-based scenarios depending on the mobile environment and validation requirement.
How can AI assist with mobile service degradation analysis?
AI-assisted analysis combines validation results, anomalies and available network evidence into a concise operational assessment. Where the evidence is insufficient for a reliable conclusion, the analysis should identify the observations without inventing a root cause.
Can Degust complement existing mobile service-assurance and network-monitoring systems?
Yes. Degust can provide its own operational views, export validation data and integrate selected information into existing environments. Its role is to add controlled distributed service validation rather than require replacement of established monitoring systems.