Inspect below the signalling.
Open actual PHY and MAC records, then examine the decoded fields. Follow radio-layer activity alongside RLC, PDCP and RRC messages.
Configure a mobile network, run calls and data sessions, and inspect messages from the UE, radio and core. all in your browser!
Network execution + live analysis
4G LTE5G NSA5G SANothing is simulated or pre-loaded. Enjoy real logs.
Open actual PHY and MAC records, then examine the decoded fields. Follow radio-layer activity alongside RLC, PDCP and RRC messages.
Follow requests and responses between participating nodes. Inspect the core-side exchanges behind registration, sessions and service setup.
Locate an event in time, then examine the messages around it. Follow what led up to a rejection or interrupted procedure.
Check procedure completion, timing and available DL/UL indicators alongside the records. Missing measurements stay empty.
Real records generated by the run, with decoded fields, sequence and timing. See recorded examples and protocol coverage.
Start with a preset or compose your own sequence. Run the procedure, inspect its messages, then change the conditions for your next investigation.
Select a scenario to explore.
Follow attachment or registration through bearer or PDU session setup. Inspect the exchanges that establish a data connection.
Run originating and terminating (MO/MT) call scenarios and exchange SMS over IMS. Follow setup, media and release between subscribers.
Send pings or run a download. Relate the generated traffic to its messages, latency and available throughput measurements.
Investigate handover between compatible cells, or explore how NSA adds an NR secondary cell through EN-DC.
Request and release a dedicated QoS flow. Inspect the policy and session exchanges produced by the configured 5G core.
Stop a core function or reconnect a UE. Examine what changes, what fails and how the network responds.
Attach or registration, bearer or PDU session setup, UE capability enquiry, IMS registration, MO/MT calls, two-way voice media, SMS over IMS, ping, downloads, UE reconnect and core-function stop/start.
LTE and NSA use EPC bearers; SA uses PDU sessions.
Calls and messaging require IMS and two subscribers. Handover is available in LTE and SA with compatible cells. EN-DC uses an LTE anchor and NR secondary cell in NSA. Dedicated QoS flow requests and releases require AF setup in SA.
Available actions depend on the selected technology, nodes and configuration. Read the scenario documentation.
Choose the nodes and radio settings, then combine actions and delays. Save your configuration and sequence for the next investigation.
Run a private network, exercise real scenarios and inspect the exchanges from radio to core. Use the same environment for engineering investigations, technical reviews and practical training.
A real run. A trace you can examine.
Protocol engineers
Follow a failed connection, session setup or call across UE, radio and core. Find the records you need for the next debugging step.
Companies & teams
Run a prepared scenario and share its exported records. Ground the discussion in observed behaviour, without taking on local lab installation and upkeep.
Educators & students
Change a scenario, observe the messages and explain the procedure. Give learners hands-on protocol work without equipping each person with a dedicated test rig.
Reopen a saved run with its messages, decoded fields and analysis views.
Download packet captures for further packet-level investigation.
Export structured records for scripts, analysis and reporting.
Follow a procedure across nodes, inspect the response and use the trace to decide what to test next.
Bring exported records into reviews. Reuse prepared experiments for demonstrations and onboarding.
Run a call or data session, inspect its messages, then let learners change the conditions and investigate.
Yes. Each run starts a network environment. The analyzer displays records generated during that run and decoded from its captures. How a run works.
Each run has its own core, subscriber data and address space. Saved run history belongs to your account. Run isolation.
A browser and a Trace5G account. Choose LTE, SA or NSA, configure the lab and start a run. The progress panel shows startup before records arrive.
Yes. Each finished run stays in your history with its decoded trace. Open it again in the analyzer, or export it as JSON or a packet capture.
Contact us to learn more about the platform or discuss a business opportunity.
CONTACT UScontact@trace5g.com